System and methods for self-adjusting electronic reconciliation of a contribution amount and delivery value

ABSTRACT

Embodiments of the present disclosure are directed to a system, methods, and computer-readable media for a self-regulating and self-adjusting reconciliation of a cumulative contribution amount and a cumulative delivery value determined for instances associated with an entity.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a nonprovisional that claims the benefit ofpriority to U.S. Provisional App. No. 62/789,297, filed on 7 Jan. 2019and entitled “System and Methods for Self-Adjusting ElectronicReconciliation of a Contribution Amount and Delivery Value,” and alsoclaims the benefit of priority to U.S. Provisional App. No. 62/800,828,filed on 4 Feb. 2019 and entitled “System and Methods for Self-AdjustingElectronic Reconciliation of a Contribution Amount and Delivery Value,”both of which are incorporated by reference in its entirety herein.

SUMMARY

Various embodiments of the present disclosure are directed to a system,methods, and computer-readable media for a self-regulating andself-adjusting reconciliation of a cumulative contribution amount and acumulative delivery value for an entity.

In embodiments, a computer-implemented method is provided. In accordancewith the method, a selected instance (e.g., e-commerce transaction)fulfilled by an entity is determined to correspond to a first class of adefined index having a plurality of defined classes. An instance valueassociated with the selected instance is determined to belong to a firsttier of the index, the first tier having an instance value range. Theinstance value is then multiplied by a defined baseline ratio that isassociated with the first class and the first tier of the defined index.In embodiments, a delivery value associated with a delivery of theinstance, such as the instance fulfilled by the entity and determined tocorrespond to the first class, is calculated. The method calculates, inan embodiment, a cumulative contribution amount of the instancefulfilled by the entity during a predetermined period of time. Inembodiments, the method further calculates a cumulative delivery valueof deliveries associated with a plurality of instances during thepredetermined period of time. The method then facilitates an electronicreconciliation of the cumulative contribution amount with the cumulativedelivery value for the entity for the predetermined period of time.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described the disclosure in general terms, reference willnow be made to the accompanying drawings, which are not necessarilydrawn to scale, and wherein:

FIG. 1 provides an exemplary environment in accordance with embodimentof the present disclosure;

FIG. 2 provides an exemplary server in accordance with embodiments ofthe present disclosure;

FIGS. 3A-B illustrate a flowchart of an exemplary computer-implementedmethod in accordance with embodiments of the present disclosure;

FIG. 4 illustrates a flowchart of an exemplary computer-implementedmethod in accordance with embodiments of the present disclosure;

FIG. 5 illustrates a flowchart of an exemplary computer-implementedmethod in accordance with embodiments of the present disclosure;

FIG. 6 illustrates a flowchart of an exemplary computer-implementedmethod in accordance with embodiments of the present disclosure;

FIG. 7 illustrates a flowchart of an exemplary computer-implementedmethod in accordance with embodiments of the present disclosure;

FIG. 8 provides an illustration of another exemplary environment inaccordance with embodiments of the present disclosure;

FIG. 9 provides an illustrative schematic of an exemplary computingentity in accordance with an embodiment of the present disclosure;

FIG. 10 provides an illustrative schematic of an exemplary mobilecomputing entity in accordance with an embodiment of the presentdisclosure;

FIG. 11 illustrates an exemplary autonomous vehicle in accordance withan embodiment of the present disclosure;

FIG. 12 illustrates an exemplary manual vehicle in accordance with anembodiment of the present disclosure;

FIG. 13 illustrates an exemplary conveying mechanism in accordance withan embodiment of the present disclosure; and

FIG. 14 illustrates an exemplary image capture system in accordance withan embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

The present disclosure will now be described more fully hereinafter withreference to the accompanying drawings, in which some, but not allembodiments of the disclosure are shown. Indeed, the disclosure can beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Rather, these embodiments areprovided so that this disclosure will satisfy applicable legalrequirements. Like numbers refer to like elements throughout.

Exemplary System Operation

Various embodiments of the present disclosure improve these existingtechnologies in at least the following ways. Utilizing the systems andcomputer-implemented methods described herein, entities can be providedwith increasingly accurate and predictable estimations of accruingshipping, handling, insurance, and delivery amounts while maintainingthe privacy of proprietary carrier-side actual cost determinations. Anindex from which such estimations are determined can be dynamicallyupdated on a periodic basis based on actual costs and predictedestimations, such that a fair distribution of costs can be automaticallydetermined for subsequent settlements. Existing and conventionaltechnologies fail to capture these aspects.

Beginning with FIG. 1, an exemplary environment 100 is provided. Theenvironment 100 comprises a plurality of servers in communication withone another, directly and/or indirectly, using wired and/or wirelessconnections. The plurality of servers includes a control server 102, oneor more entity servers 104 and 106 hosting one or more e-commerceentities, and a carrier server 108 hosting a carrier entity. The carrierserver 102 can communicate with mobile devices 112, in some embodiments.The environment 100 further comprises a client device 110 incommunication with the one or more entity servers 104 and 106 hostingthe e-commerce entities.

At a high level, an instance is generated by the entity server 104 basedon a communication (e.g., an e-commerce order for items) received fromthe client device 110. Although referred to as an “entity” server, itwill be understood that the server can be an e-commerce server thathandles (e.g., receives, facilitates, processes) transactions for anynumber of entities. The instance, among other instances, is communicatedfrom the entity server 104 to the control server 102. The control server102 selects the instance for processing and reconciliation. The controlserver 102 can select an instance on or after the expiration of apredetermined period of time, or alternatively, on an on-going basiswhen the instance is received from the entity server 104. The instanceitself is associated with a value. The value can be determined by theentity corresponding to or hosted by the entity server 104 and/or by apurchaser corresponding to or hosted by the client device 110. Forexample, the value of the instance can comprise the retail or wholesalepricing of one or more items associated with that instance, and/or othercosts and fees as determined between the entity, the purchaser, and/orthe carrier entity. The value can be used to identify a definedpercentage or ratio, or baseline ratio, of the total value of the itemsin the order used to generate the instance. The defined baseline ratiois obtained by referencing a carrier-defined index having variousdefined entity classes and pricing tiers. In some aspects, the classesand pricing tiers can be manually or dynamically defined. The definedbaseline ratio is obtained by aligning the value of the order from whichthe instance was generated with a pricing tier in the defined index, andaligning the entity associated with the instance with an entity class inthe defined index, wherein the alignment identifies a defined baselineratio that is specific to the combination of the pricing tier and entityclass, as further explained hereinafter.

Once selected, the control server 102 reconciles the instance bycalculating the value provided (e.g., paid) by the entity ascompensation for the shipping, handling, insurance, and/or delivery ofitems ordered in the instance relative to the value of thecarrier-determined cost of the shipping, handling, insurance, and/ordelivery of the items ordered in the instance. In embodiments, the valueprovided by the entity as compensation for the shipping, handling,insurance, and/or delivery of items ordered in the instance is referredto as the contribution amount, as discussed in detail hereinafter. Thecontribution amount is generally calculated by multiplying the value ofthe order from which the instance was generated by the defined baselineratio obtained from the carrier-defined index (e.g., by the alignmentmentioned above). The value or contribution amount provided by theentity as compensation for the shipping, handling, insurance, and/ordelivery of items ordered in the instance can be collected by thecarrier and/or a third party at any time, whether prior or subsequent tothe actual shipping, handling, insurance, and/or delivery of itemsordered in the instance. The carrier-determined cost refers to thecarrier-determined pricing for the shipping, handling, insurance, and/ordelivery of items ordered in the instance. The carrier-determinedpricing generally exceeds the actual cost incurred by the carrier todrive a profit for the carrier. However, it is contemplated that in someinstances, the pricing can match the actual cost incurred or the pricingcan be lower than the actual cost incurred. Additionally, inembodiments, the value of the carrier-determined cost of the shipping,handling, insurance, and/or delivery of the items ordered in theinstance is referred to as the delivery amount, as discussed in detailhereinafter. As the control server 102 reconciles the contributionamount provided by the entity and the delivery value determined by thecarrier, the control server 102 can calculate a deficit or a surplus. Insome embodiments, a determined deficit can be optionally “written off”or recouped by requesting additional value from the entity and a surpluscan be distributed to the carrier, a third party, and/or the entity, invarious embodiments. In some embodiments, the surplus can be distributedto the purchaser associated with an instance (e.g., transaction for anitem) and/or the intended recipient of an item.

Once the control server 102 determines the reconciliation, the controlserver 102 can communicate the reconciliation information to the carrierserver 108. In further embodiments, the entity server 104 can receive acommunication from the control server 102 regarding a determineddeficit, for example. The carrier server 108 can communicate a requestfor additional value to the entity server 104, or another third party,for example. In some other embodiments, a third party can receive acommunication from the control server 102 regarding a determinedsurplus, for example, such that the surplus determined from thereconciliation can be distributed to one or more of the carrier of thecarrier server 108 and/or a third party. In some instances, thedistribution of surplus can be provided using fiat currency. Thedistribution can be facilitated utilizing electronic bankingtransactions, which can be automated based on the determined surplus, orfacilitated through a workflow having values defined based on thedetermined surplus. Additionally or alternatively, the distribution ofsurplus can be provided, for example, by distributing (e.g.,electronically generating transactions for transferring) virtual orcrypto-currency (e.g., BITCOIN™, Ethereum®, Litecoin, RIPPLE®, Dogecoin,and/or the like), in some embodiments. Similarly, the distribution ofsurplus utilizing such alternative methods of payment can be automatedbased on the determined surplus, or facilitated through a workflowhaving values defined based on the determined surplus.

Based on the reconciliation performed via the control server 102, thedefined baseline ratios, pricing tiers, and entity classes can bedynamically modified in order to adjust for anticipated deficits and/orsurpluses for subsequently performed reconciliations of later selectedinstances. Based on the reconciliation, the control server 102 candetermine that there is a deficit instead of a surplus, and the controlserver 102 can change the particular baseline ratio that corresponds tothe combination of class and tier, from which the deficit was createdfor corresponding instances, by increasing the baseline ratio, forexample, to reduce the deficit for future instances evaluated in futureperiods of time. In another example, the control server 102 candetermine that there is a surplus of revenue, and the control server 102can change the particular baseline ratio that corresponds to thecombination of class and tier, from which the surplus was generated forcorresponding instances, by decreasing the baseline ratio, for example,to reduce (while maintaining at least some margin of) the surplus forfuture instances evaluated in future periods of time.

In accordance with embodiments described herein, references to aninstance, an index, an order, a value, a baseline, an amount, a tier, aclass, and the like, can be defined as an electronic data object orother electronic data structure that is defined, stored, and/orgenerated by a computing device.

Turning to FIG. 2, an exemplary diagram of a computing device is shown.Generally, the computing device corresponds to the control server 102.The control server 102 can comprise a communications interface 200. Inembodiments, the communications interface 200 can receive an instancefrom entity server 104 during a predetermined period of time, whereinthe received instance includes a defined instance value. The instancecan be generated, for example, at the entity server 104 in response to acommunication (e.g., an electronic internet-based purchase of one ormore items) received from a client device 110.

The control server 102 can further comprise an instance assignmentmodule 202. The instance assignment module 202 can access and referencea defined index. The index can comprise a plurality of defined classes,a plurality of defined tiers, and a plurality of defined baselineratios. In some embodiments, the classes, tiers, and baseline ratios inthe index can be defined by the control server 102 acting at the requestof the carrier and/or carrier server 108. Generally, each of theplurality of defined tiers can comprise an instance value range. In oneembodiment, the instance value ranges can correspond to a retail valueor a wholesale value, for example, as defined by an entity and/or entityserver 104. As such, the instance value can be defined by the entity orthe purchaser, or by a negotiated agreement between the entity and thepurchaser, for example. Additionally, each of the plurality of definedbaseline ratios can be associated with a particular combination of adefined class and a defined tier in the defined index. As used herein,“defined” indicates that a thing is predetermined, predefined, set,static, and/or otherwise prior to the receipt of the instance, forexample.

The instance assignment module 202 can determine a defined class and adefined tier to which the received instance is to be assigned, and thus,can further assign a defined baseline ratio to the instance based on theclass and tier assignment, as described in detail hereinafter. As such,in an embodiment, the instance assignment module 202 can determine thatthe received instance corresponds to a first class of the defined indexhaving the plurality of defined classes, the plurality of defined tiers,and the plurality of defined baseline ratios. Generally, the receivedinstance can be determined to correspond to a first class based onentity characteristics associated with the received instance. Forexample, when the received instance corresponds to an e-commercetransaction between a client and an entity that sells automobilereplacement parts, the entity can correspond to a particular definedclass based on the entity's association with automobile replacementparts. In another example, when the received instance corresponds to ane-commerce transaction between a client and an entity that sellsautomobile replacement parts, the entity can correspond to a particulardefined class based on the volume of the entity's consumption of carrierservices for shipment of the automobile replacement parts being sold. Assuch, one or more classes can be specialized and defined by one or moreentity characteristics or characteristics of items associated with theentity. An entity associated with one or more instances generated fromorders for items having particular dimensions, weight, fragility, and/orrisk (e.g., volatile materials) defined as characteristics associatedwith the items can be used to assign the received instance associatedwith the particular entity to the first class. Additionally oralternatively, delivery distance, pickup location, delivery location,speed of delivery service (e.g., overnight delivery versus grounddelivery), and/or mode of delivery defined as characteristics associatedwith items can be used to assign the received instance to the firstclass.

The instance assignment module 202 can determine that the receivedinstance is associated with a particular entity by using the data of theinstance, in embodiments, to identify the entity. Further, the instanceassignment module 202 can determine that the particular entity isassociated with one specific class in the index, in embodiments.

In some embodiments, an entity can be associated with one of theplurality of classes, either based on an initial instance being receivedand/or concurrent with or prior in time, for example, when registeringthe entity for participation in the reconciliation program. For example,one or more entities can register with the control server 102 or“onboard” to the reconciliation program, and the one or more entitiescan provide information that is then used to assign each of the one ormore entities to a corresponding class in the index. In one embodiment,the entity provides an average order (or instance) value. Additionally,in some embodiments, the entity provides an average order (or instance)weight. The entity can then be assigned to a class without requiringadditional item type, dimensions, or sales information. In anotherembodiment, the entity provides an average order weight, an averageorder value, and an average number of orders per month at onboarding andregistering. Additionally, the entity can provide a location, from whichitems are to originate as shipments, for example, as part of onboardingand registering. The entity can provide additional information such as,in various embodiments, one or more of a number of actual orders to bereceived and/or completed within a predetermined period of time (e.g.,per month, per quarter, per a first quarter of a year, per a lastquarter of a year, annually, bi-monthly), a predicted number of ordersfor a predetermined period of time, an average order value (e.g.,corresponding to instance value), an average order weight, actual totalorder values for a predetermined period of time, a predicted total ordervalue for a predetermined period of time, or the like. The additionalinformation of the entity at onboarding and/or the initial instancereceived can include an actual weight associated with an item to beshipped for an order, for example. Additional information can specify aproduct type or item class that is associated with one or more ordershandled by the entity. For example, whether the item is a piece offurniture, jewelry, sports equipment, grocery, home décor, or the like.The control server 102 can use part or all of the aforementionedinformation to assign each entity to one of the plurality of classes inthe index, in embodiments.

Using the weight associated with an item corresponding to an initialinstance or order for a particular entity, for example, the controlserver 102 can assign the particular entity to a particular class. In afurther embodiment, using the weight associated with an itemcorresponding to an instance for a particular entity and the number ofactual (e.g., historical order and/or sales data) or predicted orders tobe received and/or completed within a predetermined period of time forthe particular entity, the control server 102 can assign the particularentity to one of the plurality of classes. The class can be selected bythe control server 102, for example, wherein the class reflects apredicted cumulative delivery value for the predetermined period oftime. When an instance is received, the entity can be identified usingthe instance, in some embodiments, and the class is identified that isassociated with the entity.

The instance assignment module 202 can further determine the definedinstance value included in the received instance corresponds to a firstinstance value range of one of the plurality of defined tiers. When eachdefined tier corresponds to a specific instance value range, theinstance value of the received instance can be matched to the specificinstance value range of a particular defined tier. For example, when theinstance value corresponds to $201.57 for the items of the order used togenerate the instance, the received instance can be determined to matchwith or belong to a defined tier having a defined instance value rangedefined as values from $150.00 up to $250.00.

The instance assignment module 202 can also determine that the receivedinstance is associated with a first baseline ratio of the plurality ofdefined baseline ratios based on the received instance corresponding tothe first class and the defined instance value corresponding to thefirst instance value range of one of the plurality of defined tiers. Asmentioned above, each of the plurality of defined baseline ratios can beassociated with a particular combination of a defined class and adefined tier in the defined index. As such, by determining that thereceived instance belongs to the first class based on thecharacteristics of the entity of the received instance corresponding tothe first class, and by further determining that the instance value ofthe received instance corresponds to a particular defined tier, abaseline ratio can be identified as corresponding to the combination ofthe first class and the particular defined tier. Said baseline ratio canthus be associated with or assigned to the received instance.

Additionally, in further embodiments, the instance assignment module 202can automatically flag the received instance when the instancecorresponds to a particular product type or item class, and when thatparticular product type or item class is associated with a deviation inshipment cost, relative to other instances of the same or similarinstance value (e.g., the same or similar tier in the index). In someembodiments, the instance received includes a stock keeping unit (SKU)and the SKU is utilized to identify the product type or item class. Forexample, one or more product types or one or more item classes can beassociated with, or predefined by a carrier as corresponding to, ashipment cost that is predicted to or has historically been appraised asmeeting or exceeding a threshold (i.e., a deviation relative to amajority of other instances in a particular tier). Such product types oritem classes correspond to items where the baseline ratio of thecorresponding tier does not accurately account for the actual cost ofshipment, relative to at least a majority of instances received that aresimilarly sorted into the same tier (i.e., that item class is predictedto cause a surplus or deficit at reconciliation using the baseline tierof the specific tier). For example, the product type or item class cancorrespond to items where the actual cost of shipment relative to theinstance value is such that the baseline ratio of the tier for theinstance value and entity combination produces or is predicted toproduce a relatively large surplus or deficit at reconciliation,relative to a majority of the other instances sorted into the same tier.In one example, a particular product type or item class can be costlyfor the carrier to ship due to one or more of weight, bulk, or shipmentorigination location, relative to the corresponding instance value(purchase price for the item), or alternatively, the particular producttype or item class can be relatively cheap for the carrier to shiprelative to the corresponding instance value (e.g., small lightweightitems of high value). The automatically flagged instances can be furthersorted into a specialized tier in the index that is specific to theproduct type or item class. The specialized tier can have a baselineratio that is specific to one or more particular product types or itemclasses.

Continuing, the control server 102 can comprise a reconciliation module204. The reconciliation module 204 can perform the following operationsbased on the determinations of class, tier, and/or baseline ratiodetermined by the instance assignment module 202. In some embodiments,the reconciliation module 204 of the control server 102 can determine orcalculate a contribution value that is associated with the receivedinstance. The contribution value can be based on the defined instancevalue multiplied by the first baseline ratio determined to be associatedwith the received instance. As described herein, the contribution amountcan correspond to a carrier-defined fixed percentage of the instancevalue, though the baseline ratio can be adjusted subsequently toeffectuate changes to the contribution amount of one or more receivedinstances. The contribution value, being a fixed percentage of theinstance value, for example, can correspond to a value to be paid by theentity associated with the received instance and/or purchaser associatedwith the received instance as payment for shipping, handling, insurance,and/or delivery of one or more items in the order for which the instancewas generated at the entity server 104. Alternatively, the contributionamount can be determined by and received from an e-commerce entityand/or a third party that communicates with the e-commerce entity, forexample, via the entity server 104.

The reconciliation module 204 can also calculate a delivery valueassociated with the received instance. A delivery value can becalculated based on shipping, handling, insurance, and/or delivery datareceived, for example, from a carrier through the carrier server 108. Insome embodiments, the communications interface 200 can obtain one ormore delivery values from a carrier, for example, via the carrier server108. In various embodiments, the delivery value can be predicted,estimated, or an actual “known” value. For example, a predicted deliveryvalue can be determined for those instances that correspond to an orderthat has been placed with the entity but for which delivery isdetermined not yet completed by the carrier entity at the close of apredetermined period of time (e.g., an end-of-quarter) forreconciliation. For example, for an instance, items determined as beingtransported internationally and/or domestically by ground can be furtherdetermined as in mid-transit at the end-of-quarter reconciliation, suchthat a carrier-determined delivery value is estimated. In anotherembodiment, the delivery value can correspond to an actual deliveryvalue, calculated by tracking one or more parcels of the items of anorder throughout their handling and delivery through the carrier'sdelivery network. By way of non-limiting example, for an instance, itemsdetermined as being transported via expedited carrier services (e.g.,overnight shipping, three-day shipping) are likely to be completedwithin a short time period of order placement, such that the actualcarrier-determined delivery value can be known before or by the close ofthe predetermined period of time for reconciliation.

It will be understood that calculating the contribution value and/or thedelivery value can be performed for a plurality of instances receivedfrom an e-commerce entity, for example, via the entity servers 104 and106, for example. However, independent of the quantity of instancesreceived, the reconciliation module 204 can calculate a cumulativecontribution amount associated with the entity server 104 and/or 106based on the calculated contribution value associated with the receivedinstance and a determined expiration or conclusion of the predeterminedperiod of time. For example, when a plurality of instances are receivedfrom the entity server 104 for an entity during the predetermined periodof time, the reconciliation module 204 of the control server 102 canindividually determine contribution amounts for each received instance,and then can be aggregated or sum all the contribution amounts togetherto generate a cumulative contribution amount for one entity for theinstances received during the predetermined period of time. In someembodiments, the cumulative contribution amount can be calculated, forexample, upon a determination of the expiration of the predeterminedperiod of time by the control server 102.

The reconciliation module 204 can also calculate a cumulative deliveryvalue associated with the predetermined period of time, wherein thecumulative delivery value is calculated based on a determined deliveryvalue associated with the received instance. For example, when aplurality of instances are received from the entity server 104 for anentity during the predetermined period of time, the reconciliationmodule 204 of the control server 102 can individually determine deliveryvalues for each received instance, and then can be aggregated or sum allthe delivery values together to generate a cumulative delivery value forone entity for the instances received during the predetermined period oftime. In some embodiments, the cumulative delivery value can becalculated, for example, based upon a determination of the expiration ofthe predetermined period of time by the control server 102.Subsequently, the reconciliation module 204 reconciles the calculatedcumulative contribution amount with the calculated cumulative deliveryvalue for the predetermined period of time, in some embodiments.

[ ].

FIGS. 3-6 illustrate flow diagrams of exemplary methods in accordancewith the embodiments discussed herein. It will be understood that each“block” or “step” in the flowcharts, and combinations of steps in theflowcharts, can be implemented by various means, such as hardware,firmware, processor, circuitry, and/or other devices associated withexecution of software including one or more computer programinstructions. For example, one or more of the methods described can beembodied by computer program instructions. In this regard, the computerprogram instructions which embody the methods can be stored by a memoryof an apparatus employing an embodiment of the present invention andexecuted by a processor of an apparatus. As will be appreciated, anysuch computer program instructions can be loaded onto a computer orother programmable apparatus (e.g., hardware) to produce a machine, suchthat the resulting computer or other programmable apparatus implementsthe functions specified in the flowchart steps. These computer programinstructions can also be stored in a computer-readable memory that candirect a computer or other programmable apparatus to function in aparticular manner, such that the instructions stored in thecomputer-readable memory produce an article of manufacture, theexecution of which implements the functions specified in the flowchartblocks. The computer program instructions can also be loaded onto acomputer or other programmable apparatus to cause a series of operationsto be performed on the computer or other programmable apparatus, inorder to produce a computer-implemented process such that theinstructions executed on the computer or other programmable apparatusprovide operations for implementing the functions specified in theflowchart blocks.

FIGS. 3A-B depict a flowchart of an exemplary computer-implementedmethod 300 described in accordance with some embodiments of the presentdisclosure. In various embodiments, the computer-implemented method 300can be performed using an application programming interface (API) orplatform, which can interface with any of the computing devices and/orcomponents or modules described herein. The computer-implemented method300 can be performed by processing logic that comprises hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (e.g., instructions run on a processor to perform hardwaresimulation), firmware, or a combination thereof. In some embodiments,one or more non-transitory computer-readable media storecomputer-executable instructions that, when executed by one or morecomputing devices, cause the one or more computing devices or modulesthereof to perform the computer-implemented method 300. The followingdescription is provided for exemplary purposes only.

In accordance with the computer-implemented method 300, the methodreceives, by a computing device, an instance from an entity serverduring a predetermined period of time, wherein the received instanceincludes a defined instance value, shown at block 302. In an embodiment,the computing device can include a module, such as communicationsinterface 200 of FIG. 2, which can receive an instance from an entityserver during a predetermined period of time, wherein the receivedinstance includes a defined instance value. For example, based on acommunication received from a client computing device, thatcommunication specifying an e-commerce order for one or more items thatare “placed” in an electronic shopping cart and purchased from theentity using an electronic payment between the purchaser and entity or athird party, an entity server can generate an instance for the order.The instance can be communicated from the entity server 104, and thusreceived by the control server 102, for example.

At block 304, the computer-implemented method 300 determines, by thecomputing device, that the received instance corresponds to a firstclass of a defined index having a plurality of defined classes, aplurality of defined tiers, and a plurality of defined baseline ratios,each of the plurality of defined tiers comprising an instance valuerange, and each of the plurality of defined baseline ratios beingassociated with a particular combination of a defined class and adefined tier. In an embodiment, the computing device can include amodule, such as instance assignment module 202 of FIG. 2, whichdetermines that the received instance corresponds to a first class of adefined index having a plurality of defined classes, a plurality ofdefined tiers, and a plurality of defined baseline ratios. In someembodiments, the instance can be determined to belong to a first classbased on the entity corresponding to the instance and order. In oneexample, the entity can be previously registered with a platform or API,wherein the entity has been previously associated with the first classbased on a characteristic of the entity, the entity's items, and/or theentity's carrier-specific consumption. In another example, the entitycan be determined to be associated with the first class based on thereceived instance, or based on one or more instances received within aspecific predetermined period of time.

At block 306, the computer-implemented method 300 determines, by thecomputing device, the defined instance value included in the receivedinstance corresponds to a first instance value range of one of theplurality of defined tiers. Generally, the instance value can bedetermined based on a value assigned to the order from which theinstance was generated. For example, when the electronic shopping cartof the purchaser as a whole is assigned a value of $85.67, the instancegenerated can comprise the instance value of at least $85.67. Based onthe instance value, the defined instance value tiers in the index caninclude a particular tier having an instance value range of $50.00 up to$100.00, for example. As such, the computer-implemented method 300 candetermine, in this example, that the defined instance value correspondsto this particular instance value range, and thus, to said particulartier in the index. In an embodiment, the computing device can include amodule, such as instance assignment module 202 of FIG. 2, whichdetermines the defined instance value included in the received instancecorresponds to a first instance value range of one of the plurality ofdefined tiers.

At block 308, the computer-implemented method 300 determines, by thecomputing device, that the received instance is associated with a firstbaseline ratio of the plurality of defined baseline ratios based on thereceived instance corresponding to the first class and the definedinstance value corresponding to the first instance value range of one ofthe plurality of defined tiers. In an embodiment, the computing devicecan include a module, such as instance assignment module 202 of FIG. 2,that determines that the received instance is associated with a firstbaseline ratio of the plurality of defined baseline ratios based on thereceived instance corresponding to the first class and the definedinstance value corresponding to the first instance value range of one ofthe plurality of defined tiers. Using the index, a baseline ratio orpercentage is determined that corresponds to both the determined classof the instance and the determined tier of the instance. For example,for entities that correspond to the first class conducting instanceshaving values within the first instance value tier of the instance valuerange of $50.00 up to $100.00, the baseline ratio of 4.95% can beassigned to this combination in the index. As such, in the example, thebaseline ratio is determined for the received instance.

At block 310, the computer-implemented method 300 calculates, by thecomputing device, a contribution value associated with the receivedinstance based on the defined instance value multiplied by the firstbaseline ratio determined to be associated with the received instance.In an embodiment, the computing device can include a module, such asreconciliation module 204 of FIG. 2, that calculates a contributionvalue associated with the received instance based on the definedinstance value multiplied by the first baseline ratio determined to beassociated with the received instance. Additionally, at block 312, thecomputer-implemented method 300 calculates, by the computing device, adelivery value associated with the received instance. In an embodiment,the computing device can include a module, such as reconciliation module204 of FIG. 2, which calculates a delivery value associated with thereceived instance. The delivery value associated with the receivedinstance can be determined by predicting, estimating, and/or tracking(e.g., based on near real-time information as items from the order thatgenerated the instance travel through a carrier's shipping network afterhand-off from the entity for delivery to the purchaser or recipient) thecost incurred for shipping, handling, insuring, and/or delivery of theitems ordered from the entity via the electronic shopping cart, ascorresponding to an order from which the received instance wasgenerated. Additionally or alternatively, the delivery value associatedwith the received instance can be determined by automatically predictingand/or estimating a probability that an item can be returned, whereinthe probability of an item being returned is calculated based on thepurchaser, the entity, a class, an instance value, and/or a commoditytype of the item. In accordance with various embodiments, the foregoingcharacteristics can be defined as variables (e.g., values) associatedwith the item or a unique identifier associated with the item.

It will be understood that calculating the contribution value and/or thedelivery value can be performed for a plurality of instances received.However, independent of the quantity of instances received, at block314, the computer-implemented method 300 calculates, by the computingdevice, a cumulative contribution amount associated with the entityserver based on the calculated contribution value associated with thereceived instance and a determined conclusion of the predeterminedperiod of time. In an embodiment, the computing device can include amodule, such as reconciliation module 204 of FIG. 2, which calculates acumulative contribution amount associated with the entity server basedon the calculated contribution value associated with the receivedinstance and a determined conclusion of the predetermined period oftime. At block 316, the computer-implemented method 300 calculates, bythe computing device, a calculated cumulative delivery value associatedwith the predetermined period of time, wherein the cumulative deliveryvalue is calculated based on a determined delivery value associated withthe received instance. In an embodiment, the computing device caninclude a module, such as reconciliation module 204 of FIG. 2, whichcalculates a calculated cumulative delivery value associated with thepredetermined period of time.

At block 318, the computer-implemented method 300 reconciles, by thecomputing device, the calculated cumulative contribution amount with thecalculated cumulative delivery value for the predetermined period oftime. In an embodiment, the computing device can include a module, suchas reconciliation module 204 of FIG. 2, which reconciles the calculatedcumulative contribution amount with the calculated cumulative deliveryvalue for the predetermined period of time. For example, thecomputer-implemented method 300 determines a difference between thecalculated cumulative contribution amount and the calculated cumulativedelivery value, in order to determine whether the instance generated asurplus of revenue for the carrier, or a deficit of cost for thecarrier. Based on the reconciliation, the computer-implemented method300 can modify the defined index, including the classes, tiers, and/orbaseline ratios in order to effectuate changes in the handling ofsubsequently received instances from the entity and/or other entities,as described hereinafter.

For example, when the difference between the calculated cumulativecontribution amount and the calculated cumulative delivery value is suchthat the instance generated a surplus of revenue for the carrier, thecomputer-implemented method 300 can modify the defined index bydecreasing a baseline ratio that corresponds to a particular combinationof one of the plurality of classes and one of the plurality of tiers. Insome embodiments, the baseline ratio can be decreased by a definedpercentage or value within the index, thus redefining the baseline ratiofor subsequent instances. As such, when the surplus of revenue isdetermined to meet or exceed a predefined threshold value (e.g., exceedsby 4% and 10%), the index can be updated by decreasing the baselineratio that corresponds to the combination of the first class of theplurality of classes and the tier that corresponds to the first instancevalue range. In one embodiment, the baseline ratio is decreased by nomore than 0.5%, 1%, or 5% for any one predetermined period of time.Then, the updated index can be used for future instance(s) evaluatedduring a subsequent period of time, wherein the decreased baseline ratiois predicted to bring a cumulative contribution amount closer in valueto the cumulative delivery value for that subsequent predeterminedperiod of time, in some embodiments. As such, the updated index ispredicted to reduce the surplus of revenue based on the decreasedbaseline ratio for the particular combination of a class and a tier, inembodiments. In one example, the baseline ratio is decreased by anamount that is predicted to place the cumulative contribution amountwithin a predefined percentage, range, and/or margin of the cumulativedelivery value.

In another example, when the difference between the calculatedcumulative contribution amount and the calculated cumulative deliveryvalue is such that the instance generated a deficit of cost for thecarrier (e.g., deficit meets or exceeds 1% to 10%), thecomputer-implemented method 300 can modify the defined index byincreasing a baseline ratio that corresponds to a particular combinationof one of the plurality of classes and one of the plurality of tiers.Then, the updated index can be used for future instance(s) evaluatedduring a subsequent period of time, wherein the increased baseline ratiois predicted to bring a cumulative contribution amount closer in valueto the cumulative delivery value for the subsequent predetermined periodof time, in some embodiments. As such, the updated index is predicted toreduce the deficit of cost and/or generate a surplus of revenue for thecarrier based on the increased baseline ratio for the particularcombination of a class and a tier, in embodiments. In one example, thebaseline ratio is increased by an amount that is predicted to place thecumulative contribution amount within a predefined percentage, range,and/or margin of the cumulative delivery value.

Turning now to FIG. 4, a flowchart of an exemplary method is describedin accordance with an embodiment of the present disclosure. The method400 can be performed by processing logic that comprises hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (e.g., instructions run on a processor to perform hardwaresimulation), firmware, or a combination thereof. In some embodiments,one or more non-transitory computer-readable media storecomputer-executable instructions that, when executed by one or morecomputing devices, cause the one or more computing devices to performthe method 400. In some embodiments, the method 400 is performed using acomputing device, such as can comprise the control server 102 shown inFIGS. 1 and 2. The following description is provided for exemplarypurposes only.

At block 402, the method 400 comprises determining an instance valuemultiplied by a baseline ratio associated with the first class of theindex. Multiplying the instance value by the baseline ratio produces acontribution amount that can be remitted from an entity for theshipping, handling, insurance, and/or delivery of one or more item(s)that are the subject of an instance corresponding to the instance value.In an embodiment, the method 400 determines, by a computing device, aninstance value multiplied by a baseline ratio associated with the firstclass of the index. In such an embodiment, the computing device caninclude a module, such as the instance assignment module 202 and/or thereconciliation module 204 of FIG. 2, which determines an instance valuemultiplied by a baseline ratio associated with the first class of theindex. As explained further below, the instance value multiplied by thebaseline ratio can be determined for each of one or more instancesfulfilled by an entity, the entity corresponding to a first class of anindex, the index having a plurality of classes including the firstclass. Generally, an entity refers to an entity having a web-basedpresence for conducting e-commerce. Exemplary entities include a retailbusiness, a wholesale business, a seller, a merchant, a vendor, and/or awebsite or application user conducting an auction, resale, and/orconsignment. The entity can also be a consumer of carrier services, inan embodiment. Carrier services include shipping, handling, insurance,and/or transport of items which are the subject of an instance and whichare to be transported by the carrier for delivery to a recipient, forexample. E-commerce generally refers to conducting retail and/orwholesale instances involving the sale of items or services provided bythe entity. As used herein, “instance” and “transaction” are usedinterchangeably.

Generally, an entity can be assigned a class within an index, the indexcomprising a plurality of classes and a plurality of tiers. In someembodiments, the index can be a structured schedule that is structuredas a table of one or more entity classes and one or more pricing tiers.The tiers can be customized for each class, in some embodiments. Inother embodiments, the tiers are consistent across the plurality ofclasses. The index can provide a relationship between classes andpricing tiers, such that one or more classes are associated with one ormore particular pricing tiers and some tiers are associated with one ormore classes. A class refers to a group, wherein the group can bedefined using characteristics of one or more of: an entity, an item,item combinations, instance(s), recipients of an item, purchasers of anitem, carrier services consumed by an entity, and/or carrier servicesthat are specific to an item and/or entity, for example.

The method 400 can determine that the entity corresponds to a firstclass of the index based on the characteristics associated with theentity, associated with items of the entity, and/or associated withinstances of said entity, in some embodiments. The index can comprise aplurality of classes, each class being defined by one or more common,shared, or related characteristics. The method 400 can determine thatthe entity corresponds to a first class by determining one or more of anaverage parcel volume for the entity, an average delivery zone for itemsprovided by the entity, an overall delivery density associated with theentity, or a seasonal delivery density associated with the entity. In afurther embodiment, the method 400 can determine that the entitycorresponds to a first class of the index having a plurality ofcharacteristic classes by determining an average parcel weightassociated with the entity, the items of the entity, and/or instancesassociated with the entity. In some instances, the average parcel weightcharacteristics can be determined by a carrier, as opposed to the entityitself. Generally, the characteristics of the entity, instances, items,and/or carrier services associated with the items and/or instances canbe electronically encoded as metadata, tags, and/or tokens, in anembodiment. In some embodiments, characteristics of parcels for item(s)of an instance can be obtained based on information and data gathered,generated, or otherwise received via an autonomous vehicle, a manualvehicle, a conveying mechanism, and/or an image capture system, asdiscussed later regarding FIGS. 9-13. Additionally or alternatively,such characteristics can be encoded and exchanged using a blockchain tomaintain a decentralized and immutable electronic ledger of instances,entities, carrier services, and/or characteristics. In some embodiments,the method 400 generates the index and formulates classes and tiersbased on historical instance information and historical deliveryinformation, whether stored in a database or a blockchain, for example.

With regard to the index, a tier can be defined by value(s) for sortingor categorizing instances. For example, a tier can correspond to one ormore value(s) in any denomination or currency, including virtual orcryptocurrency. Each tier can define one or more of an instance value, arange of instance values defined by a lower value limit and an uppervalue limit, an instance value threshold, an average instance value, amean instance value, and/or a mode instance value. As such, instancescan be sorted into one or more tiers based on the value corresponding tothe instance. In an embodiment, “instance value” refers to a purchaseprice or other valuation of one or more items that are the subject ofthe particular instance between the entity and a recipient or purchaser,wherein the instance value can be a price or valuation that can beagreed upon by the purchaser and the entity. As used herein, “recipient”and “purchaser” of item(s) are used interchangeable for simplicity butit will be apparent from this disclosure that in some embodiments, therecipient and the purchaser of item(s) are not the same person,individual, or entity.

Using the index, each instance can be assigned a baseline ratio based onthe instance value relative to the tiers and the entity relative to theclasses, for the instance at issue. A baseline ratio can be apredetermined ratio or percentage, in some embodiments. Generally, aspecific baseline ratio can be defined for each combination of class andtier within the index. For example, a first instance having an instancevalue of n currency and being conducted with entity A can be assignedbaseline ratio x, by assigning the first instance into a first tier thatincludes the instance value n currency, and further assigning the firstinstance to class 1 based on the characteristics of entity Acorresponding to the shared or related characteristics of class 1.

To illustrate the example, a first instance corresponding to purchaserJoe's electronic shopping cart containing a plurality of items to bepurchased from the entity Bob's Fish & Tackle has an instance value of$127.29, wherein the instance value can be the total summed value of allthe items within Joe's electronic shopping cart (e.g., retail orwholesale price of each item can be set by Bob's Fish & Tackle). In thisexample, the instance value $127.29 can correspond to a second tier inthe index and Bob's Fish & Tackle can be assigned or otherwise belong toentity class A, based on one or more of characteristics such as annualsales revenue, sales volume, carrier services purchases quarterly, orthe like of Bob's Fish & Tackle, for example. As such, using theinstance value and the entity's class to reference the index, theexemplary instance can be assigned the baseline ratio x (e.g., 2.7%) aspredefined in the index for the alignment of the pricing tier and entityclass. By aligning each instance with a tier that includes thecorresponding instance value and with a class for the entity associatedwith that instance, a baseline ratio can be determined for the instanceat issue. The baseline ratio can be determined for each and everyinstance occurring for an entity, across a plurality of entities, inembodiments. As such, for example, the method 400 locates a baselineratio and multiplies the instance value by the baseline ratio, asdiscussed regarding block 402 of the method 400. Multiplying theinstance value by the baseline ratio can be used to generate acontribution amount. The contribution amount can comprise a value to beremitted from the entity, generally, as a value corresponding to theanticipated cost of shipping, handling, insurance, and/or delivery ofthe item(s) that are the subject of the instance. The method 400 canperform the determination of block 402 for each and every instance of anentity, across a plurality of entities. Said determination can be madein an on-going manner, as instances occur and/or are fulfilled by theentity. Alternatively, said determination can be performed in batches atvarious time increments within the predetermined period of time (e.g.,every 24 hours determinations are made for all instances of the entitythat occurred within the 24 hour period of time). Further, for eachentity, the instances can be recorded and the contribution amounts canbe aggregated per entity for all instances occurring within apredetermined period of time. The instance values and/or contributionamounts can be encoded and exchanged using a blockchain to maintain adecentralized and immutable electronic ledger of the instances,entities, carrier services, and/or characteristics associated therewith,as previously described.

Continuing to block 404, the method 400 comprises, for each of one ormore instances fulfilled by the entity that corresponds to the firstclass, determining a delivery value associated with delivery of theinstance. Herein, “value” and “amount” are used interchangeably. Adelivery value can be determined by a carrier, in some embodiments. Thedelivery value, in embodiments, comprises a value and/or cost of theshipping, handling, insurance, and/or delivery of the item(s) of theparticular instance. The delivery value can comprise the value or costas incurred by the carrier (e.g., actual cost incurred without a pricemarkup), or the delivery value can comprise the value or cost for whichthe entity can be responsible (e.g., cost with a price markup).Generally, the delivery value may not be the same as the contributionamount remitted from the entity for the shipping, handling, insurance,and/or delivery of the item(s) that are the subject of the instance. Thedelivery value can be determined for each of one or more instancesfulfilled by an entity, across a plurality of entities, in someembodiments. The delivery value can be encoded and exchanged using ablockchain to maintain a decentralized and immutable electronic ledgerof the instances, entities, carrier services, and/or characteristics. Insome embodiments, characteristics of parcels for item(s) of an instanceare obtained based on information and data gathered, generated, orotherwise received via an autonomous vehicle, a manual vehicle, aconveying mechanism, and/or an image capture system, as discussed laterregarding FIGS. 9-13.

At block 406, the method 400 comprises determining a cumulativecontribution amount of the one or more instances fulfilled by the entityduring the predetermined period of time. In an embodiment, the method400 determines a cumulative contribution amount of the one or moreinstances fulfilled by the entity during the predetermined period oftime via a computing device. In such an embodiment, the computing devicecan include a module, such as the instance assignment module 202 and/orthe reconciliation module 204 of FIG. 2, which determines a cumulativecontribution amount of the one or more instances fulfilled by the entityduring the predetermined period of time. The cumulative contributionamount can be specific to one entity, in an embodiment, thusrepresenting the contribution amounts for all instances fulfilled bythat one entity within the predetermined period of time. In anotherembodiment, the cumulative contribution amount can representcontribution amounts for all instances fulfilled by a plurality ofentities with one class in the index. In yet another embodiment, thecumulative contribution amount can be a summation of contributionamounts for all instances within a particular tier of the index asfulfilled by one entity. As such, in various embodiments, the cumulativecontribution amount can be specific to contribution amounts for anentity, a tier, a class, or a combination thereof.

At block 408, the method 400 comprises determining a cumulative deliveryvalue of deliveries associated with the one or more instances fulfilledby the entity during the predetermined period of time. In an embodiment,the method 400 determines the cumulative delivery value of deliveriesassociated with the one or more instances fulfilled by the entity duringthe predetermined period of time, via a computing device. In such anembodiment, the computing device can include a module, such as theinstance assignment module 202 and/or the reconciliation module 204 ofFIG. 2, which cumulative delivery value of deliveries associated withthe one or more instances fulfilled by the entity during thepredetermined period of time. The cumulative delivery value can bespecific to one entity, in an embodiment, thus representing thevaluation (e.g., actual cost to carrier and/or carrier-determinedcharges to the entity) of shipping, handling, insurance, and/or deliveryof all items by the carrier, as corresponding to all instances fulfilledby that one entity within the predetermined period of time. In anotherembodiment, the cumulative delivery value can represent the valuation(e.g., actual cost to carrier and/or carrier-determined charges to theentity) of shipping, handling, insurance, and/or delivery of all itemsby the carrier, for the instances fulfilled for a plurality of entitieswith one class in the index. In yet another embodiment, the cumulativedelivery value can be a summation of valuation (e.g., actual cost tocarrier and/or carrier-determined charges to the entity) for theshipping, handling, insurance, and/or delivery of all items by thecarrier for all instances within a particular tier of the index asfulfilled by one entity during the predetermined period of time. Assuch, in various embodiments, the cumulative delivery value can bespecific to an entity, a tier, a class, or a combination thereof.

Continuing, at block 410, the method 400 comprises reconciling thecumulative contribution amount with the cumulative delivery value forthe entity for the predetermined period of time. Reconciliation can beautomatically performed via one or more processors on, or subsequent to,the expiration of the predetermined period of time. As such, thereconciliation-based adjustments discussed hereinafter can beautomatically implemented via one or more processors such that themethod 400 can be self-regulating and autonomous, in embodiments. In anembodiment, the method 400 reconciles, via a computing device, thecumulative contribution amount with the cumulative delivery value forthe entity for the predetermined period of time. In such an embodiment,the computing device can include a module, such as the reconciliationmodule 204 of FIG. 2, which reconciles the cumulative contributionamount with the cumulative delivery value for the entity for thepredetermined period of time.

In reconciling the cumulative contribution amount with the cumulativedelivery value for the entity for the predetermined period of time, thesurplus or deficit between the cumulative contribution amount and thecumulative delivery value can be determined. In some embodiments, basedon the reconciliation, the baseline ratio of one or more of theplurality of tiers in the index can be adjusted. For example, when thecumulative contribution amount is equal to or less than the cumulativedelivery value for the entity, the entity can be reclassified to anotherclass having a greater baseline ratio than the first class. In anotherexample, when the cumulative contribution amount is equal to or lessthan the cumulative delivery value for the entity, the baseline ratio ofthe first class can be increased for all entities within the firstclass.

In one example, when the cumulative contribution amount is greater thanthe cumulative delivery value for the entity, the entity can remain inthe first class and retain the baseline ratio. In another example, whenthe cumulative contribution amount is greater than the cumulativedelivery value for the entity, the entity can remain in the first classand the baseline ratio of the first class can be lowered. In yet anotherexample, when the cumulative contribution amount meets and/or exceedsthe cumulative delivery value for the entity by a threshold amount orthreshold percentage that can be predetermined by the carrier, forexample, the entity can remain in the first class and the baseline ratioof the first class can be lowered by a dynamic amount that isproportional to the surplus (e.g., when surplus exceeds 5% or 10%,multiply the surplus percentage by 0.5% and the lower baseline ratio bysaid factor), or a predetermined and fixed amount (e.g., between 0.025%to 1% or up to 5%).

As such, when reconciliation is performed and a deficit is determined,the deficit can be recouped by collecting currency or virtual currency,for example, from the entity or on behalf of the entity, whereinrecoupment can account for all or a portion of the deficit. Whenreconciliation is performed and a surplus is determined, the surplus canbe distributed to the carrier, the entity, and/or a third party using acurrency or virtual currency, for example. As previously discussed,using a blockchain to account for each instance, instance values,delivery values, cumulative contribution amount, cumulative deliveryvalue, deficit, and/or surplus, the reconciliation can be performed withincreased accuracy.

In embodiments, the accuracy of the reconciliation can be supported byleveraging a distributed ledger system. The methods described herein canleverage a distributed ledger system that comprises data, the data beingindicative of instances. The date can further be indicative of thephysical transfer of items associated with the instances, digital assetsassociated with the instance and/or reconciliation (e.g., valuation inany currency and/or virtual currency), and/or any combination thereof.Each instance and data for each instance can be represented as aplurality of “blocks,” wherein one block corresponds to one instance ortransaction. Each later-in-time instance can be generated as a new blockthat can be electronically added and linked to prior-in-time blocks,thus providing a linked blockchain indicative of each instance for whichdata can be stored in the distributed ledger. Moreover, each block cancomprise data identifying a particular instance, instancecharacteristics, entity, entity characteristics, an entity's carrierservices behavior (e.g., type, volume, service level used by entity whenacting as a customer of a carrier), one or more items, itemcharacteristics, currency type, value of each time, value of all itemsassociated with an instance, currency exchange rate at the time theblock is generated, average value per item, purchase, purchasercharacteristics (e.g., shopping behavior and patterns), delivery zone ofeach of the one or more items, location identifier, address, and/oraddresses that are each indicative of an entity, recipient, carrier,and/or location having prior, present, or future control over the item,in embodiments. Additionally or alternatively, each block can comprisedata identifying a particular instance, the characteristics of theinstance, one or more tiers associated with the instance, one or moreclasses associated with an entity, one or more baseline ratiosassociated with the instance, an instance value, one or morecontribution amounts, one or more delivery values, and the like, aspreviously described in detail. In various embodiments, a new block canbe generated and added to a blockchain of the distributed ledger uponreceipt of information and/or data indicating that an instance isinstantiated, an instance is in progress, and/or that an instance isbeing or has been fulfilled by an entity, and/or a change in control ofan item, for example, from an entity to a carrier, and/or from a carrierto a recipient (e.g., progressive parcel tracking using identifierscanning and near real-time location tracking of a parcel throughcarrier distribution channels and/or via delivery vehicles). It can befurther contemplated that each block can be associated with and/orinclude a timestamp that can be generated by a computing node uponreceiving a notice or data of the instance. Using the data encoded andencrypted in each block, and/or using timestamps within thepredetermined period of time, for example, the method 400 reconciles thecumulative contribution amount with the cumulative delivery value forthe entity for the predetermined period of time. As the distributedledger is immutable, accuracy of the reconciliation provides animprovement over existing technologies.

In further embodiments, based on the reconciliation, the method 400determines the entity corresponds to a second class of the index. Insuch an example, the second class can be associated with a baselineratio that can be different from the baseline ratio associated with thefirst class. In one such embodiment, the baseline ratio associated withthe second class can be greater than the baseline ratio associated withthe first class. In another embodiment, the baseline ratio associatedwith the second class can be less than the baseline ratio associatedwith the first class. The entity can be determined to correspond to thesecond class based on the characteristics of the entity, characteristicsof the instances associated with the entity, characteristics of theitems associated with the entity, and characteristics of the shipping,handling, insurance, and delivery of the items associated with theentity. Such characteristics can be encoded and stored in a database ora blockchain, for example, as previously described.

In some embodiments, the method 400 can be performed in a re-occurringfashion for a plurality of time periods and a plurality of entities,wherein each time period corresponds to the predetermined period oftime. Each entity can be separately reconciled, for example, and classadjustments can be implemented regarding each entity and the index.Based on the reconciliation, the method 400 can modify the predeterminedperiod of time for a subsequently performed reconciliation, wherein thepredetermined period of time can be adjusted based on the cumulativedelivery value for the entity. The predetermined period of time can be24 hours or more in duration. In some embodiments, the predeterminedperiod of time corresponds to two weeks, one month, three months, aquarter of a year, four months, six months, half of a year, eightmonths, or one year. In one example of adjusting the duration of thepredetermined period of time, the method 400 can modify thepredetermined period of time for one or more subsequent reconciliationsby shortening the duration of the predetermined period of time when thecumulative delivery value for the entity meets or exceeds the cumulativecontribution amount. In one such example, the duration of thepredetermined period of time for a subsequent reconciliation can beshortened when the reconciliation determines there is a deficit betweenthe cumulative contribution amount and the cumulative delivery value, inembodiments. The duration of the predetermined period of time for asubsequent reconciliation can be shortened when such a deficit reachesor exceeds a threshold amount or threshold percentage.

Additionally or alternatively, the duration of the predetermined periodof time can be shortened when a deficit is determined by reconciliationfor multiple consecutive periods of time. In another example, the method400 can modify the predetermined period of time for a subsequentreconciliation by lengthening the duration of the predetermined periodof time when the cumulative delivery value for the entity belonging tothe first class is less than the cumulative contribution amount. Assuch, the predetermined period of time for a subsequent reconciliationcan be shortened when the reconciliation determines there is a surplusbetween the cumulative contribution amount and the cumulative deliveryvalue, in embodiments. The predetermined period of time for a subsequentreconciliation can be lengthened when such a surplus reaches or exceedsa threshold amount or threshold percentage. Additionally oralternatively, the predetermined period of time can be lengthened when asurplus is determined by reconciliation for multiple consecutive periodsof time. In various embodiments, the duration of the predeterminedperiod of time can be adjusted based on one or more reconciliations forone or more entities, and/or, can further be adjusted and customized foreach tier, each class, and/or each combination of tier and class withinthe index.

Turning to FIG. 5, a flowchart of an exemplary method 500 is describedin accordance with an embodiment of the present disclosure. The method500 can be performed by processing logic that comprises hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (e.g., instructions run on a processor to perform hardwaresimulation), firmware, or a combination thereof. The followingdescription is provided for exemplary purposes only. In someembodiments, one or more non-transitory computer-readable media storecomputer-executable instructions that, when executed by one or morecomputing devices, cause the one or more computing devices to performthe method 500. As some aspects of the method 500 herein have beendescribed previously, additional description of some steps are omittedfor brevity, yet it will be understood that the description regardingthe other methods herein applies to some or all aspects of method 500.In some embodiments, the method 500 is performed using a computingdevice, such as can comprise the control server 102 and modules shown inFIGS. 1 and 2.

In embodiments, for each of a plurality of entities conductinge-commerce, the method 500 determines whether an entity corresponds to afirst class of an index having a plurality of classes, shown at block502, and as described in detail hereinabove. In an embodiment, themethod 500, for each of a plurality of entities conducting e-commerce,determines, via a computing device, whether an entity corresponds to afirst class of an index having a plurality of classes. In such anembodiment, the computing device can include a module, such as theinstance assignment module 202 of FIG. 2, which determines whether anentity corresponds to a first class of an index having a plurality ofclasses.

At block 504, the method 500 provides a baseline ratio for the entity,the baseline ratio being a predetermined value associated with the firstclass and fixed for a predetermined period of time, as previouslydescribed, based on the entity being aligned with the first class andthe instance value being aligned with a particular tier in the index. Inan embodiment, the method 500, provides, by a computing device, abaseline ratio for the entity, the baseline ratio being a predeterminedvalue associated with the first class and fixed for a predeterminedperiod of time. In such an embodiment, the computing device can includea module, such as the instance assignment module 202 of FIG. 2, whichprovides a baseline ratio for the entity.

For each of the one or more instances fulfilled by the entity, themethod 500 comprises determining an instance value multiplied by thebaseline ratio associated with the first class, as shown at block 506.In an embodiment, the method 500 determines, by a computing entity, theinstance value multiplied by the baseline ratio associated with thefirst class. In such an embodiment, the computing device can include amodule, such as the instance assignment module 202 and/or thereconciliation module 204 of FIG. 2, which determines an instance valuemultiplied by the baseline ratio associated with the first class.

Further, at block 508, the method 500 comprises determining a deliveryvalue associated with delivery of the item(s) of an instance, for eachof the one or more instances fulfilled by the entity. In an embodiment,the method 500 determines, by a computing device, a delivery valueassociated with delivery of the item(s) of an instance, for each of oneor more instances fulfilled by the entity. In such an embodiment, thecomputing device can include a module, such as the instance assignmentmodule 202 and/or the reconciliation module 204 of FIG. 2, whichdetermine a delivery value associated with delivery of the item(s) of aninstance, for each of one or more instances fulfilled by the entity.

At block 510, the method 500 determines a cumulative contribution amountof the one or more instances fulfilled by the entity during thepredetermined period of time. In an embodiment, the method 500determines, by a computing device, a cumulative contribution amount ofthe one or more instances fulfilled by the entity during thepredetermined period of time. In such an embodiment, the computingdevice can include a module, such as the instance assignment module 202and/or the reconciliation module 204 of FIG. 2, which determine thecumulative contribution amount of the one or more instances fulfilled bythe entity during the predetermined period of time.

And at block 512, the method 500 determines a cumulative delivery valueof deliveries associated with the one or more instances fulfilled by theentity during the predetermined period of time. At block 514, the method500 reconciles the cumulative contribution amount with the cumulativedelivery value for the entity for the predetermined period of time, aspreviously described. In an embodiment, the method 500 determines, by acomputing device, a cumulative delivery value of deliveries associatedwith the one or more instances fulfilled by the entity during thepredetermined period of time. In such an embodiment, the computingdevice can include a module, such as the instance assignment module 202and/or the reconciliation module 204 of FIG. 2, which determine thecumulative delivery value of deliveries associated with the one or moreinstances fulfilled by the entity during the predetermined period oftime.

In some embodiments, for each of the one or more instances fulfilled bya plurality of entities for the plurality of time periods, the method500 can monitor item-specific characteristics of each instance. Then,based on the reconciliation and the item-specific characteristicsmonitored of the one or more instances fulfilled by the plurality ofentities for the plurality of time periods, the method 500 can modifythe index by reducing the plurality of classes in number to simplify theindex. In such an embodiment, the method 500 can maintain a greatestbaseline ratio for each of the plurality of classes in the index thatremain after the reduction. The number of classes can be modified bydetermining related characteristics between the pluralities of entities,instances, items, and delivery data, for example. Additionally oralternatively, the tiers can also be adjusted and modified to be reducedor increased in number, and/or the number of tiers can be maintainedwhile the value ranges can be modified.

In another embodiment, based on the reconciliation, the method 500determines whether the entity corresponds to a second class of theindex, wherein the second class can be associated with a baseline ratiothat is different from the baseline ratio associated with the firstclass. When the method 500 determines the entity corresponds to a secondclass of the index, the entity can be assigned (e.g., re-assigned) tothe second class in the index. In further embodiments, subsequent toassigning the entity to the second class in the index, the method 500can be performed for a subsequent period of time for the entity asnow-assigned to the second class. For example, the method 500 candetermine an instance value multiplied by the baseline ratio associatedwith the second class for each of the one or more instances fulfilled bythe entity in a subsequent predetermined period of time, in such anexample. Further, the method 500 can determine a delivery valueassociated with delivery of the instance for each of the one or moreinstances fulfilled by the entity in a subsequent predetermined periodof time, in this example. Then, the method 500 can determine acumulative contribution amount of the one or more instances fulfilled bythe entity during the subsequent predetermined period of time. Themethod 500 can continue by determining a cumulative delivery value ofdeliveries associated with the one or more instances during thesubsequent predetermined period of time, in such an example. The method500 can then reconcile the cumulative contribution amount with thecumulative delivery value for the entity for the subsequentpredetermined period of time, in such embodiments.

In some embodiments, the method 500 can be performed in a reoccurringfashion for a plurality of predetermined periods of time and a pluralityof entities. As such, entities, the index, classes, tiers, and baselineratios can be modified over time to more accurately reflect thecharacteristics, previously discussed, based on the reconciliation andany surplus or deficit, as previously described. For example, in anembodiment, the method 500 reconciles the cumulative contribution amountwith the cumulative delivery value for a plurality of entities for eachof the plurality of predetermined periods of time. The method 500 canthen modify the baseline ratio associated with the first class based onreconciling the cumulative contribution amount with the cumulativedelivery value for the plurality of entities for each of the pluralityof predetermined periods of time, in some embodiments. As such, thebaseline ratio associated with the first class can be modified byincreasing the baseline ratio when, based on reconciliation, thecumulative contribution amount is equal to or less than the cumulativedelivery value, or the baseline ratio associated with the first classcan be modified by decreasing the baseline ratio, based onreconciliation, when the cumulative contribution amount exceeds thecumulative delivery value.

Turning to FIG. 6, a flowchart of an exemplary method 600 is describedin accordance with an embodiment of the present disclosure. The method600 can be performed by processing logic that comprises hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (e.g., instructions run on a processor to perform hardwaresimulation), firmware, or a combination thereof. The followingdescription is provided for exemplary purposes only. In someembodiments, one or more non-transitory computer-readable media storecomputer-executable instructions that, when executed by one or morecomputing devices, cause the one or more computing devices to performthe method 600. In another embodiment, the method 600 can be performedvia a system comprising at least one first computing device having atleast one processor, and at least one computer-readable storage mediumhaving program instructions embodied therewith, wherein the programinstructions readable or executable by at least one processor cause thesystem to perform the method 600. The computing device can comprise thecontrol server 102 shown in FIGS. 1 and 2, in some embodiments. Each ofthe modules discussed previously regarding other methods herein can beused in the same or similar manner to perform various aspects of method600, via a computing device comprising, for example, the control server102 of FIGS. 1-2. As some aspects of the method 600 herein have beendescribed previously, additional description of some steps are omittedfor brevity, yet it will be understood that the description hereinregarding other methods applies to some or all aspects of method 600.

At block 602, the method 600 determines an entity corresponds to a firstclass of a pricing index having a plurality of characteristic classes,as previously discussed. At block 604, the method 600 provides abaseline value to the entity, the baseline ratio being a predeterminedvalue associated with the first class and fixed for a predeterminedperiod of time. At block 606, for each of the one or more instancesfulfilled by the entity that corresponds to the first class, the method600 determines an instance value multiplied by the baseline ratioassociated with the first class. Additionally, the method 600 determinesa delivery value associated with delivery of the instance for each ofthe one or more instances fulfilled by the entity that corresponds tothe first class, shown at block 608. At block 610, the method 600determines a cumulative contribution amount of the one or more instancesfulfilled by the entity during the predetermined period of time, aspreviously described. At block 612, the method determines a cumulativedelivery value of deliveries associated with the one or more instancesduring the predetermined period of time. At block 614, the method 600reconciles the cumulative contribution amount with the cumulativedelivery value for the entity for the predetermined period of time, asdescribed above.

Continuing to FIG. 7, a flowchart of an exemplary method 700 isdescribed in accordance with an embodiment of the present disclosure.The method 700 can be performed by processing logic that compriseshardware (e.g., circuitry, dedicated logic, programmable logic,microcode, etc.), software (e.g., instructions run on a processor toperform hardware simulation), firmware, or a combination thereof. Thefollowing description is provided for example purposes only. In someembodiments, one or more non-transitory computer-readable media storecomputer-executable instructions that, when executed by one or morecomputing devices, cause the one or more computing devices to performthe method 700. In another embodiment, the method 700 can be performedvia a system comprising at least one first computing device having atleast one processor, and at least one computer-readable storage mediumhaving program instructions embodied therewith, wherein the programinstructions readable or executable by at least one processor cause thesystem to perform the method 700. The computing device can comprise thecontrol server 102 shown in FIGS. 1 and 2, in some embodiments. Each ofthe modules discussed previously regarding other methods herein can beused in the same or similar manner to perform various aspects of method700, via a computing device comprising, for example, the control server102 of FIGS. 1-2. As some aspects of the method 700 herein have beendescribed previously, additional description of some steps are omittedfor brevity, yet it will be understood that the description hereinregarding other methods applies to some or all aspects of method 700.

In some embodiments, subsequent to reconciling a cumulative contributionamount with a cumulative delivery value for an entity as describedhereinabove, the method 700 can be used to periodically orintermittently update the classes, tiers, and/or baseline ratiospreviously discussed. For example, using the method 700, the index fromwhich value and cost estimations are determined can be dynamicallyupdated on a periodic basis based on actual costs and predictedestimations, such that a fair distribution of costs can be automaticallydetermined for subsequent reconciliation or “settlements.” Existing andconventional technologies fail to capture these aspects.

In one example, the method 700 can be used to generate one or moreadditional tiers for handling items wherein the calculated cumulativecontribution value is less than a threshold value of the cumulativedelivery value for the predetermined period of time, in someembodiments. Additionally or alternatively, the method 700 can be usedto generate one or more additional tiers when the calculated cumulativecontribution value is less than a predefined percentage of thecumulative delivery value percentage for the predetermined period oftime, in another embodiment. Thus, in various embodiments, the method700 facilitates an automatic feedback mechanism that automaticallyupdates, modifies, and/or “corrects” the plurality of classes, theplurality of tiers, the plurality of baseline ratios, or a combinationthereof in the index, to structure the reconciliation so that thecumulative contribution amount is or is predicted to be, as determinedfor future instance(s) during a subsequent predetermined period of time,within a predefined percentage or predetermined margin (range) of thecumulative delivery value.

Beginning at block 702, subsequent to reconciling a cumulativecontribution amount with a cumulative delivery value for an entity asdescribed hereinabove, the method 700 can determine to assign orre-assign the entity associated with the instance(s) used for thereconciliation to a different class or a new class in the index.Generally, the entity (i.e., seller) can be re-assigned to a new classor a different class in the index based on whether a surplus of revenueor a deficit of cost to the carrier resulted from the reconciliation. Insome embodiments, as described with regard to method 400 of FIG. 4, forexample, based on the reconciliation, the entity can be determined tocorrespond to a second class of the index for future instances, insteadof the first class used for the prior instances within the predeterminedperiod of time. In such an example, the second class can be associatedwith a baseline ratio that can be different (e.g., greater or lower)from the baseline ratio associated with the first class. The entity canbe determined to correspond to the second class based on one or more ofthe characteristics of the entity, characteristics of the instancesassociated with the entity, characteristics of the items associated withthe entity, and/or characteristics of the shipping, handling, insurance,and delivery of the items associated with the entity. Suchcharacteristics can be encoded and stored in a database or a blockchain,for example, as previously described.

In some embodiments, the method 700 determines that the entityassociated with the instance(s) used for the reconciliation is to bere-assigned to a new class. For example, the entity may not be a good“fit” within the existing plurality of classes in the index based on theactual cost used to ship the type of items in the orders/instancesrelative to the values of the items in the orders/instances for thespecific entity and/or specific item classes being shipped by theentity. In one example, an item can have a high delivery value (costlyto ship due to one or more of weight, bulk, or location) relative to thecorresponding instance value (purchase price for the item). As such,based on the reconciliation, the entity can be re-assigned to a newclass in the index.

Alternatively, in some embodiments, an entity can be identified prior toany reconciliation, for example, when the entity registers with thecontrol server 102 to participate in a program for reconciliation,and/or when an initial instance that corresponds to the entity is firstreceived by the control server 102. In one such embodiment, the entitycan provide additional information that specifies one or more of, forexample: an actual or predicted weight of a specific item(s), an actualaverage or predicted average value for items, a number of actual orpredicted orders to be received and/or completed within a predeterminedperiod of time (e.g., per month, per quarter, per a first quarter of ayear, per a last quarter of a year, annually, bi-monthly), a total valueof sales or revenue within a predetermined period of time, a type orcategory of item sold or provided by the entity, the location of theentity, or the like, as previously discussed herein. The control server102, for example, can determine that the entity is to be assigned to anew class in the index at any time, based on the additional informationand/or one or more instances, and/or one or more reconciliationsconducted over any number of predetermined periods of time.

At block 704, the method 700 generates a new class in the index.Although discussed in the singular here for simplicity, any number ofnew classes can be generated for one entity, or for a plurality ofentities subsequent to corresponding reconciliations. In someembodiments, the new class can be assigned to one or more entities thatare identified as “outliers” that do not fit (i.e., cannot be accuratelysorted) into the existing index, for example, those entities providingitems where the actual cost used to ship the items in theorders/instances relative to the values of the items in theorders/instances produces a deficit of cost for the carrier entity. Inembodiments, the new class can be assigned to one or more entities thatare identified as outliers that do not fit into the existing index, forexample, those entities providing items where the actual cost used toship the items in the orders/instances relative to the values of theitems in the orders/instances produces a surplus of cost for the carrierentity (e.g., small lightweight items of high value).

At block 706, the entity is assigned to the new class. The associationof an entity with a particular class can be stored in a database, inembodiments, as controlled by the carrier entity, in an embodiment. Atblock 708, the method 700 determines one or more new baseline ratiosthat correspond to a combination of the new class and each of theplurality of tiers within the index. In some embodiments, the baselineratio is calculated using the surplus or deficit determined from theprior reconciliation, for example, wherein the baseline ratio isdetermined to reduce the surplus or reduce the deficit predicted infuture reconciliations. Additionally or alternatively, the baselineratio of the new class can be a percentage within a range of thebaseline ratio of the first class to which the entity was previouslydetermined to belong. In one example, the new baseline ratio iscalculated by increasing or decreasing the existing baseline ratio ofthe first class to which the entity had previously corresponded by apercentage in the range of 0.01% and 5.0%. In another example, the newbaseline ratio is associated with a “cap” that cannot be exceeded, suchas, 1.5% of the baseline ratio that was most recently previouslyassigned to the entity. The percentage and/or range of percentage usedto calculate the new baseline ratio for the new class can be based onthe cumulative delivery value determined for one or more instancesassociated with the entity.

Accordingly, when one or more instances are subsequently received for afuture predetermined period of time, for example, the instances can bedetermined to correspond to the new class based on the instances'association with the particular entity and/or a particular item class,and based on the instance value, the new baseline ratio can be used tocalculate the contribution value for one or more subsequently receivedinstances during a future predetermined period of time. In embodiments,when an instance that is associated with the entity is subsequentlyreceived, the method 700 determines that the instance corresponds to theentity and the new class to which the entity was assigned, shown atblock 710. The assignment and re-assignment of an entity to a differentexisting class or to a new class can be performed at any time and anynumber of times, whether at onboarding into the reconciliation program,based on receipt of an instance, or after one or more reconciliationshave been completed for one or more different periods of times.

The exemplary methods illustrated in FIGS. 3-7 can, for example, beperformed using or communicating with the systems and/or devicesdescribed hereinafter. In this regard, a system and/or device candirectly or indirectly, perform the steps, blocks, and/or operationsthrough the use of one or more of processing elements, non-volatilememory, and volatile memory. It will be understood that the systemand/or device comprises a set of hardware components or hardwarecomponents coupled with software components configured to autonomouslyor automatically perform the methods described previously, in someembodiments. Such components can, for instance, utilize a processingelement to execute operations, and can utilize non-volatile memory tostore computer code executed by the processing element, as well as tostore relevant intermediate or ultimate output of the system orapparatus. It should also be appreciated that, in some embodiments, thesystem and/or device can include a separate processor, speciallyconfigured field programmable gate array (FPGA) or application specificinterface circuit (ASIC), to perform its corresponding functions. Inaddition, computer program instructions and/or other type of code can beloaded onto a computer, processor, or other programmable apparatus'scircuitry to produce a machine, such that the computer, processor, orother programmable circuitry can execute the code on the machine tocreate the means for implementing the various functions described inconnection with the shipper behavior prediction engine.

Moreover, although values with regard to percentages have been discussedherein in the relative scale of zero to 10%, it will be understood thatany percentage scale is contemplated to be within the scope of theinvention.

The details of one or more embodiments of the subject matter describedin this specification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages of thesubject matter will become apparent from the description, the drawings,and the claims.

Computer Program Products, Methods, and Computing Entities

Embodiments of the present disclosure can be implemented in variousways, including as computer program products that comprise articles ofmanufacture. A computer program product can include a non-transitorycomputer-readable storage medium storing applications, programs, programmodules, scripts, source code, program code, object code, byte code,compiled code, interpreted code, machine code, executable instructions,and/or the like (also referred to herein as executable instructions,instructions for execution, program code, and/or similar terms usedherein interchangeably). Such non-transitory computer-readable storagemedia include all computer-readable media (including volatile andnon-volatile media).

In one embodiment, a non-volatile computer-readable storage medium caninclude a floppy disk, flexible disk, hard disk, solid-state storage(SSS) (e.g., a solid state drive (SSD), solid state card (SSC), solidstate module (SSM)), enterprise flash drive, magnetic tape, or any othernon-transitory magnetic medium, and/or the like. A non-volatilecomputer-readable storage medium can also include a punch card, papertape, optical mark sheet (or any other physical medium with patterns ofholes or other optically recognizable indicia), compact disc read onlymemory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc(DVD), Blu-ray disc (BD), any other non-transitory optical medium,and/or the like. Such a non-volatile computer-readable storage mediumcan also include read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), flash memory (e.g.,Serial, NAND, NOR, and/or the like), multimedia memory cards (MMC),secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF)cards, Memory Sticks, and/or the like. Further, a non-volatilecomputer-readable storage medium can also include conductive-bridgingrandom access memory (CBRAM), phase-change random access memory (PRAM),ferroelectric random-access memory (FeRAM), non-volatile random-accessmemory (NVRAM), magneto-resistive random-access memory (MRAM), resistiverandom-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory(SONOS), floating junction gate random access memory (FJG RAM),Millipede memory, racetrack memory, and/or the like.

In one embodiment, a volatile computer-readable storage medium caninclude random access memory (RAM), dynamic random access memory (DRAM),static random access memory (SRAM), fast page mode dynamic random accessmemory (FPM DRAM), extended data-out dynamic random access memory (EDODRAM), synchronous dynamic random access memory (SDRAM), doubleinformation/data rate synchronous dynamic random access memory (DDRSDRAM), double information/data rate type two synchronous dynamic randomaccess memory (DDR2 SDRAM), double information/data rate type threesynchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamicrandom access memory (RDRAM), Twin Transistor RAM (TTRAM), Thyristor RAM(T-RAM), Zero-capacitor (Z-RAM), Rambus in-line memory module (RIMM),dual in-line memory module (DIMM), single in-line memory module (SIMM),video random access memory (VRAM), cache memory (including variouslevels), flash memory, register memory, and/or the like. It will beappreciated that where embodiments are described to use acomputer-readable storage medium, other types of computer-readablestorage media can be substituted for or used in addition to thecomputer-readable storage media described above.

As should be appreciated, various embodiments of the present disclosurecan also be implemented as methods, apparatus, systems, computingdevices/entities, computing entities, and/or the like. As such,embodiments of the present disclosure can take the form of an apparatus,system, computing device, computing entity, and/or the like executinginstructions stored on a computer-readable storage medium to performcertain steps or operations. However, embodiments of the presentdisclosure can also take the form of an entirely hardware embodimentperforming certain steps or operations.

Embodiments of the present disclosure are described below with referenceto block diagrams and flowchart illustrations. Thus, it should beunderstood that each block of the block diagrams and flowchartillustrations can be implemented in the form of a computer programproduct, an entirely hardware embodiment, a combination of hardware andcomputer program products, and/or apparatus, systems, computingdevices/entities, computing entities, and/or the like carrying outinstructions, operations, steps, and similar words used interchangeably(e.g., the executable instructions, instructions for execution, programcode, and/or the like) on a computer-readable storage medium forexecution. For example, retrieval, loading, and execution of code can beperformed sequentially such that one instruction is retrieved, loaded,and executed at a time. In some exemplary embodiments, retrieval,loading, and/or execution can be performed in parallel such thatmultiple instructions are retrieved, loaded, and/or executed together.Thus, such embodiments can produce specifically configured machinesperforming the steps or operations specified in the block diagrams andflowchart illustrations. Accordingly, the block diagrams and flowchartillustrations support various combinations of embodiments for performingthe specified instructions, operations, or steps.

Exemplary System Architecture

FIG. 8 provides an illustration of an exemplary embodiment of thepresent disclosure. As shown in FIG. 8, this particular embodiment caninclude a manual vehicle 800, a computing entity 802, mobile computingentities 804 a, 804 b, 804 c, 804 d, 804 e, and 804 f (i.e., 804 a-f), asatellite 806, an autonomous vehicle 810, a network 812, and/or aninformation/data collection device 814 (e.g., telematics device). Eachof these components, entities, devices, systems, and similar words usedherein interchangeably can be in direct or indirect communication with,for example, one another over the same or different wired or wirelessnetworks. Additionally, while FIG. 8 illustrates the various systementities as separate, standalone entities, the various embodiments arenot limited to this particular architecture. Furthermore, although shownin the singular, it will be understood from this description that eachcomponent can occur in the plural.

1. Exemplary Computing Entities

FIG. 9 provides a schematic of a computing entity 802 according toparticular embodiments of the present disclosure. In general, the termscomputing entity, computer, entity, device, system, and/or similar wordsused herein interchangeably can refer to, for example, one or morecomputers, computing entities, desktops, mobile phones, tablets,phablets, notebooks, laptops, distributed systems, consoles inputterminals, servers or server networks, blades, gateways, switches,processing devices, processing entities, set-top boxes, relays, routers,network access points, base stations, the like, and/or any combinationof devices or entities adapted to perform the functions, operations,and/or processes described herein. Such functions, operations, and/orprocesses can include, for example, transmitting, receiving, processing,displaying, storing, determining, creating/generating, monitoring,evaluating, comparing, operating on and/or similar terms used hereininterchangeably. In particular embodiments, these functions, operations,and/or processes can be performed on data, content, information/data,and/or similar terms used herein interchangeably.

As indicated, in particular embodiments, the computing entity 802 canalso include one or more communications interfaces 900 for communicatingwith various computing entities, such as by communicating data, content,information/data, and/or similar terms used herein interchangeably thatcan be transmitted, received, operated on, processed, displayed, stored,and/or the like. As shown in FIG. 9, in particular embodiments, thecomputing entity 802 can include or be in communication with aprocessing element 902 (also referred to as processors, processingcircuitry, and/or similar terms used herein interchangeably) thatcommunicate with other elements within the computing entity 802 via abus, for example. As will be understood, the processing element 902 canbe embodied in a number of different ways. For example, the processingelement 902 can be embodied as one or more complex programmable logicdevices (CPLDs), microprocessors, multi-core processors, co-processingentities, application-specific instruction-set processors (ASIPs),microcontrollers, and/or controllers. Further, the processing element902 can be embodied as one or more other processing devices orcircuitry. The term circuitry can refer to an entirely hardwareembodiment or a combination of hardware and computer program products.Thus, the processing element 902 can be embodied as integrated circuits,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), programmable logic arrays (PLAs), hardwareaccelerators, other circuitry, and/or the like. As will therefore beunderstood, the processing element 902 can be configured for aparticular use or configured to execute instructions stored in volatileor non-volatile media 904 or otherwise accessible to the processingelement 902. As such, whether configured by hardware or computer programproducts, or by a combination thereof, the processing element 902 can becapable of performing steps or operations according to embodiments ofthe present disclosure when configured accordingly.

In particular embodiments, the computing entity 802 can further includeor be in communication with non-volatile media 904 (also referred to asnon-volatile storage, memory, memory storage, memory circuitry, and/orsimilar terms used herein interchangeably). In particular embodiments,the non-volatile storage or memory can include one or more non-volatilestorage or memory media, including but not limited to hard disks, ROM,PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks,CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory,racetrack memory, and/or the like. As will be recognized, thenon-volatile storage or memory media can store databases (e.g., itemdatabase), database instances, database management systems, data,applications, programs, program modules, scripts, source code, objectcode, byte code, compiled code, interpreted code, machine code,executable instructions, and/or the like. The term database, databaseinstance, database management system, and/or similar terms used hereininterchangeably can refer to a collection of records or information/datathat is stored in a computer-readable storage medium using one or moredatabase models, such as a hierarchical database model, network model,relational model, entity—relationship model, object model, documentmodel, semantic model, graph model, and/or the like.

In particular embodiments, the computing entity 802 can further includeor be in communication with volatile media 906 (also referred to asvolatile storage, memory, memory storage, memory circuitry and/orsimilar terms used herein interchangeably). In particular embodiments,the volatile storage or memory can also include one or more volatilestorage or memory media, including but not limited to RAM, DRAM, SRAM,FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM,TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, registermemory, and/or the like. As will be recognized, the volatile storage ormemory media can be used to store at least portions of the databases,database instances, database management systems, data, applications,programs, program modules, scripts, source code, object code, byte code,compiled code, interpreted code, machine code, executable instructions,and/or the like being executed by, for example, the processing element902. Thus, the databases, database instances, database managementsystems, data, applications, programs, program modules, scripts, sourcecode, object code, byte code, compiled code, interpreted code, machinecode, executable instructions, and/or the like can be used to controlcertain aspects of the operation of the computing entity 802 with theassistance of the processing element 902 and operating system.

As indicated, in particular embodiments, the computing entity 802 canalso include one or more communications interfaces 900 for communicatingwith various computing entities, such as by communicatinginformation/data, content, information/data, and/or similar terms usedherein interchangeably that can be transmitted, received, operated on,processed, displayed, stored, and/or the like. Such communication can beexecuted using a wired information/data transmission protocol, such asfiber distributed information/data interface (FDDI), digital subscriberline (DSL), Ethernet, asynchronous transfer mode (ATM), frame relay,information/data over cable service interface specification (DOCSIS), orany other wired transmission protocol. Similarly, the computing entity802 can be configured to communicate via wireless external communicationnetworks using any of a variety of protocols, such as general packetradio service (GPRS), Universal Mobile Telecommunications System (UMTS),Code Division Multiple Access 2000 (CDMA2000), CDMA2000 1× (1×RTT),Wideband Code Division Multiple Access (WCDMA), TimeDivision-Synchronous Code Division Multiple Access (TD-SCDMA), Long TermEvolution (LTE), Evolved Universal Terrestrial Radio Access Network(E-UTRAN), Evolution-Data Optimized (EVDO), High Speed Packet Access(HSPA), High-Speed Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi),Wi-Fi Direct, 802.16 (WiMAX), ultra wideband (UWB), infrared (IR)protocols, near field communication (NFC) protocols, Wibree, Bluetoothprotocols, wireless universal serial bus (USB) protocols, long range lowpower (LoRa), LTE Cat M1, NarrowBand IoT (NB IoT), and/or any otherwireless protocol.

Although not shown, the computing entity 802 can include or be incommunication with one or more input elements, such as a keyboard input,a mouse input, a touchscreen/display input, motion input, movementinput, audio input, pointing device input, joystick input, keypad input,and/or the like. The computing entity 802 can also include or be incommunication with one or more output elements (not shown), such asaudio output, video output, screen/display output, motion output,movement output, and/or the like.

As will be appreciated, one or more of the components of the computingentity 802 can be located remotely from other components of thecomputing entity 802, such as in a distributed system. Furthermore, oneor more of the components can be combined and additional componentsperforming functions described herein can be included in the computingentity 802. Thus, the computing entity 802 can be adapted to accommodatea variety of needs and circumstances. As will be recognized, thesearchitectures and descriptions are provided for exemplary purposes onlyand are not limiting to the various embodiments.

2. Exemplary User Computing Entity

Mobile computing entities 804 a-f can be configured for autonomousoperation and/or for operation by a user (e.g., a vehicle operator,delivery personnel, customer, and/or the like). In certain embodiments,mobile computing entities 804 a-f can be embodied as handheld computingentities, such as mobile phones, tablets, personal digital assistants,and/or the like, that can be operated at least in part based on userinput received from a user via an input mechanism. Moreover, mobilecomputing entities 804 a-f can be embodied as onboard vehicle computingentities, such as central vehicle electronic control units (ECUs),onboard multimedia system, and/or the like that can be operated at leastin part based on user input. Such onboard vehicle computing entities canbe configured for autonomous and/or nearly autonomous operation however,as they can be embodied as onboard control systems for autonomous orsemi-autonomous vehicles, such as unmanned aerial vehicles (UAVs),robots, and/or the like. As a specific example, mobile computingentities 804 a-f can be utilized as onboard controllers for UAVsconfigured for picking-up and/or delivering packages to variouslocations, and accordingly such mobile computing entities 804 a-f can beconfigured to monitor various inputs (e.g., from various sensors) andgenerate various outputs (e.g., control instructions received by variousvehicle drive mechanisms). It should be understood that variousembodiments of the present disclosure can comprise a plurality of mobilecomputing entities 804 a-f embodied in one or more forms (e.g., handheldmobile computing entities, vehicle-mounted mobile computing entities,and/or autonomous mobile computing entities).

As will be recognized, a user can be an individual, a family, a company,an organization, an entity, a department within an organization, arepresentative of an organization and/or person, and/or the like—whetheror not associated with a carrier. In one embodiment, a user can operateone or more of the mobile computing entities 804 a-f that can includeone or more components that are functionally similar to those of themanual vehicle 800.

FIG. 10 provides an illustrative schematic representative of one of themobile computing entities 804 a-f that can be used in conjunction withembodiments of the present disclosure. In general, the terms device,system, computing entity, entity, and/or similar words used hereininterchangeably can refer to, for example, one or more computers,computing entities, desktops, mobile phones, tablets, phablets,notebooks, laptops, distributed systems, vehicle multimedia systems,autonomous vehicle onboard control systems, watches, glasses, key fobs,radio frequency identification (RFID) tags, ear pieces, scanners,imaging devices/cameras (e.g., part of a multi-view image capturesystem), wristbands, kiosks, input terminals, servers or servernetworks, blades, gateways, switches, processing devices, processingentities, set-top boxes, relays, routers, network access points, basestations, the like, and/or any combination of devices or entitiesadapted to perform the functions, operations, and/or processes describedherein. Mobile computing entities 804 a-f can be operated by variousparties, including carrier personnel (sorters, loaders, deliverydrivers, network administrators, and/or the like). As shown in FIG. 10,the mobile computing entities 804 a-f can include an antenna 1000, atransmitter 1002 (e.g., radio), a receiver 1004 (e.g., radio), and aprocessing device 1006 (e.g., CPLDs, microprocessors, multi-coreprocessors, co-processing entities, ASIPs, microcontrollers, and/orcontrollers) that provides signals to and receives signals from thetransmitter 1002 and receiver 1004, respectively.

The signals provided to and received from the transmitter 1002 andreceiver 1004, respectively, can include signaling information inaccordance with air interface standards of applicable wireless systems.In this regard, the mobile computing entities 804 a-f can be capable ofoperating with one or more air interface standards, communicationprotocols, modulation types, and access types. More particularly, themobile computing entities 804 a-f can operate in accordance with any ofa number of wireless communication standards and protocols, such asthose described above with regard to the manual vehicle 800. In aparticular embodiment, the mobile computing entities 804 a-f can operatein accordance with multiple wireless communication standards andprotocols, such as UMTS, CDMA2000, 1×RTT, WCDMA, TD-SCDMA, LTE, E-UTRAN,EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR, NFC, Bluetooth,USB, and/or the like. Similarly, the mobile computing entities 804 a-fcan operate in accordance with multiple wired communication standardsand protocols, such as those described above with regard to the manualvehicle 800 via a network interface 1008.

Via these communication standards and protocols, the mobile computingentities 804 a-f can communicate with various other entities usingconcepts such as Unstructured Supplementary Service information/data(USSD), Short Message Service (SMS), Multimedia Messaging Service (MMS),Dual-Tone Multi-Frequency Signaling (DTMF), and/or Subscriber IdentityModule Dialer (SIM dialer). The mobile computing entities 804 a-f canalso download changes, add-ons, and updates, for instance, to itsfirmware, software (e.g., including executable instructions,applications, program modules), and operating system.

According to one embodiment, the mobile computing entities 804 a-f caninclude location determining aspects, devices, modules, functionalities,and/or similar words used herein interchangeably. For example, themobile computing entities 804 a-f can include outdoor positioningaspects, such as a location module adapted to acquire, for example,latitude, longitude, altitude, geocode, course, direction, heading,speed, universal time (UTC), date, and/or various otherinformation/data. In one embodiment, the location module can acquireinformation/data, sometimes known as ephemeris information/data, byidentifying the number of satellites in view and the relative positionsof those satellites (e.g., using global positioning systems (GPS)). Thesatellites can be a variety of different satellites, including Low EarthOrbit (LEO) satellite systems, Department of Defense (DOD) satellitesystems, the European Union Galileo positioning systems, the ChineseCompass navigation systems, Indian Regional Navigational satellitesystems, and/or the like. This information/data can be collected using avariety of coordinate systems, such as the Decimal Degrees (DD);Degrees, Minutes, Seconds (DMS); Universal Transverse Mercator (UTM);Universal Polar Stereographic (UPS) coordinate systems; and/or the like.Alternatively, the location information can be determined bytriangulating the position of the mobile computing entities 804 a-f inconnection with a variety of other systems, including cellular towers,Wi-Fi access points, and/or the like. Similarly, the mobile computingentities 804 a-f can include indoor positioning aspects, such as alocation module adapted to acquire, for example, latitude, longitude,altitude, geocode, course, direction, heading, speed, time, date, and/orvarious other information/data. Some of the indoor systems can usevarious position or location technologies including RFID tags, indoorbeacons or transmitters, Wi-Fi access points, cellular towers, nearbycomputing devices/entities (e.g., smartphones, laptops) and/or the like.For instance, such technologies can include the iBeacons, Gimbalproximity beacons, Bluetooth Low Energy (BLE) transmitters, NFCtransmitters, and/or the like. These indoor positioning aspects can beused in a variety of settings to determine the location of someone orsomething to within inches or centimeters.

The mobile computing entities 804 a-f can also comprise a user interface(that can include a display 1010 coupled to the processing device 1006)and/or a user input interface (coupled to a processing device 1006). Forexample, the user interface can be a user application, browser, userinterface, and/or similar words used herein interchangeably executing onand/or accessible via the mobile computing entities 804 a-f to interactwith and/or cause display of information from the manual vehicle 800, asdescribed herein. The user input interface can comprise any of a numberof devices or interfaces allowing the mobile computing entities 804 a-fto receive information/data, such as a keypad 1012 (hard or soft), atouch display, voice/speech or motion interfaces, or other input device.In some embodiments including a keypad 1012, the keypad 1012 can include(or cause display of) the numeric (i.e., 0-9) and related keys (e.g., #,*), and other keys used for operating the mobile computing entities 804a-f, and can include a full set of alphabetic keys or set of keys thatcan be activated to provide a full set of alphanumeric keys. In additionto providing input, the user input interface can be used, for example,to activate or deactivate certain functions, such as screen saversand/or sleep modes.

As shown in FIG. 10, the mobile computing entities 804 a-f can alsoinclude an camera 1014, imaging device, and/or similar words used hereininterchangeably (e.g., still-image camera, video camera, IoT enabledcamera, IoT module with a low resolution camera, a wireless enabled MCU,and/or the like) configured to capture images. The mobile computingentities 804 a-f can be configured to capture images via the camera1014, and to store those imaging devices locally, such as in thevolatile memory 1016 and/or non-volatile memory 1018 of the mobilecomputing entities 804 a-f. As discussed herein, the mobile computingentities 804 a-f can be further configured to match the captured imagedata with relevant location and/or time information captured via thelocation determining aspects to provide contextual information/data,such as a time-stamp, date-stamp, location-stamp, and/or the like to theimage data reflective of the time, date, and/or location at which theimage data was captured via the camera 1014. The contextual data can bestored as a portion of the image (such that a visual representation ofthe image data includes the contextual data) and/or can be stored asmetadata associated with the image data that can be accessible tovarious computing entities. Additionally or alternatively, the imageand/or contextual data can be stored in association with an instanceand/or delivery of an instance, for example, using blockchaintechnology.

The mobile computing entities 804 a-f can include other inputmechanisms, such as scanners (e.g., barcode scanners), microphones,accelerometers, RFID readers, and/or the like configured to capture andstore various information types for the mobile computing entities 804a-f. For example, a scanner can be used to capture item information/datafrom an item indicator disposed on a surface of a shipment or otheritem. In certain embodiments, the mobile computing entities 804 a-f canbe configured to associate any captured input information/data, forexample, via the processing device 1006. For example, scan data capturedvia a scanner can be associated with image data captured via the camera1014 such that the scan data is provided as contextual data associatedwith the image data.

The mobile computing entities 804 a-f can also include volatile memory1016 and/or non-volatile memory 1018, which can be embedded and/or canbe removable. For example, the non-volatile memory 1018 can be ROM,PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks,CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory,racetrack memory, and/or the like. The volatile memory 1016 can be RAM,DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory,register memory, and/or the like. The volatile memory 1016 andnon-volatile memory 1018 can store databases, database instances,database management systems, information/data, applications, programs,program modules, scripts, source code, object code, byte code, compiledcode, interpreted code, machine code, executable instructions, and/orthe like to implement the functions of the mobile computing entities 804a-f. As indicated, this can include a user application that is residenton the entity or accessible through a browser or other user interfacefor communicating with the manual vehicle 800 and/or various othercomputing entities. In another embodiment, the mobile computing entities804 a-f can include one or more components or functionality that are thesame or similar to those of the manual vehicle 800, as described ingreater detail above. As will be recognized, these architectures anddescriptions are provided for exemplary purposes only and are notlimiting to the various embodiments.

3. Exemplary Mobile Computing Entities

The mobile computing entities 804 a-f can be configured for autonomousoperation (e.g., in association with the autonomous vehicle 810) and/orfor operation by a user (e.g., a vehicle operator, delivery personnel,customer, and/or the like). In certain embodiments, mobile computingentities 804 a-f can be embodied as handheld computing entities, such asmobile phones, tablets, personal digital assistants, and/or the like,that can be operated at least in part based on user input received froma user via an input mechanism. Moreover, mobile computing entities 804a-f can be embodied as onboard vehicle computing entities, such ascentral vehicle electronic control units (ECUs), onboard multimediasystem, and/or the like that can be operated at least in part based onuser input. Such onboard vehicle computing entities can be configuredfor autonomous and/or nearly autonomous operation however, as they canbe embodied as onboard control systems for autonomous or semi-autonomousvehicles, such as unmanned aerial vehicles (UAVs), robots, and/or thelike. As a specific example, mobile computing entities 804 a-f can beutilized as onboard controllers for UAVs configured for picking-upand/or delivering packages to various locations, and accordingly suchmobile computing entities 804 a-f can be configured to monitor variousinputs (e.g., from various sensors) and generate various outputs (e.g.,control instructions received by various vehicle drive mechanisms).

As will be recognized, a user can be an individual, a family, a company,an organization, an entity, a department within an organization, arepresentative of an organization and/or person, and/or the like,whether or not associated with a carrier. In particular embodiments, auser can operate one or more of the mobile computing entities 804 a-fthat can include one or more components that are functionally similar tothose of the computing entity 802. FIG. 10 provides an illustrativeschematic representative of a singular of the mobile computing entities804 a-f that can be used in conjunction with embodiments of the presentdisclosure. In general, the terms device, system, computing entity,entity, and/or similar words used herein interchangeably can refer to,for example, one or more computers, computing entities, desktops, mobilephones, tablets, phablets, notebooks, laptops, distributed systems,vehicle multimedia systems, autonomous vehicle onboard control systems,watches, glasses, key fobs, radio frequency identification (RFID) tags,ear pieces, scanners, imaging devices/cameras (e.g., part of amulti-view image capture system), wristbands, kiosks, input terminals,servers or server networks, blades, gateways, switches, processingdevices, processing entities, set-top boxes, relays, routers, networkaccess points, base stations, the like, and/or any combination ofdevices or entities adapted to perform the functions, operations, and/orprocesses described herein. Mobile computing entities 804 a-f can beoperated by various parties, including carrier personnel (sorters,loaders, delivery drivers, network administrators, and/or the like). Asshown in FIG. 10, the mobile computing entities 804 a-f can include anantenna 1000, a transmitter 1002, a receiver 1004, and a processingdevice 1006 that provides signals to and receives signals from thetransmitter 1002 and receiver 1004, respectively. As discussedhereinafter, statements made in regard to the mobile computing entities804 a-f in the plural can also refer to a singular mobile computingentity, and the use of singular or plural form is not intended to beconstrued as a limitation, but serves only as a grammatical choice forconsistency throughout this description.

The signals provided to and received from the transmitter 1002 and thereceiver 1004, respectively, can include signaling information inaccordance with air interface standards of applicable wireless systems.In this regard, the mobile computing entities 804 a-f can be capable ofoperating with one or more air interface standards, communicationprotocols, modulation types, and access types. More particularly, themobile computing entities 804 a-f can operate in accordance with any ofa number of wireless communication standards and protocols, such asthose described above with regard to the computing entity 802. In aparticular embodiment, the mobile computing entities 804 a-f can operatein accordance with multiple wireless communication standards andprotocols, such as UMTS, CDMA2000, 1×RTT, WCDMA, TD-SCDMA, LTE, E-UTRAN,EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR, NFC, Bluetooth,USB, and/or the like. Similarly, the mobile computing entities 804 a-fcan operate in accordance with multiple wired communication standardsand protocols, such as those described above with regard to thecomputing entity 802 via the network interface 1008.

According to particular embodiments, the mobile computing entities 804a-f can include location determining aspects, devices, modules,functionalities, and/or similar words used herein interchangeably. Forexample, the mobile computing entities 804 a-f can include outdoorpositioning aspects, such as a location module adapted to acquire, forexample, latitude, longitude, altitude, geocode, course, direction,heading, speed, universal time (UTC), date, and/or various otherinformation/data. In particular embodiments, the location module canacquire information/data, sometimes known as ephemeris information/data,by identifying the number of satellites in view and the relativepositions of those satellites (e.g., using global positioning systems(GPS)). The satellites can be a variety of different satellites.Alternatively, the location information can be determined bytriangulating the position of one or more of the mobile computingentities 804 a-f in connection with a variety of other systems,including cellular towers, Wi-Fi access points, and/or the like.Similarly, the mobile computing entities 804 a-f can include indoorpositioning aspects, such as a location module adapted to acquire, forexample, latitude, longitude, altitude, geocode, course, direction,heading, speed, time, date, and/or various other information/data. Someof the indoor systems can use various position or location technologiesincluding RFID tags, indoor beacons or transmitters, Wi-Fi accesspoints, cellular towers, nearby computing devices/entities (e.g.,smartphones, laptops) and/or the like. For instance, such technologiescan include the iBeacons, Gimbal proximity beacons, Bluetooth Low Energy(BLE) transmitters, NFC transmitters, and/or the like. These indoorpositioning aspects can be used in a variety of settings to determinethe location of someone or something to within inches or centimeters.

The mobile computing entities 804 a-f can also comprise a user interfaceand/or a user input interface. For example, the user interface can be auser application, browser, user interface, and/or similar words usedherein interchangeably executing on and/or accessible via the mobilecomputing entities 804 a-f to interact with and/or cause display ofinformation from the computing entity 802, as described herein. The userinput interface can comprise any of a number of devices or interfacesallowing the mobile computing entities 804 a-f to receiveinformation/data, such as a keypad 1012 (hard or soft), a touch display,voice/speech or motion interfaces, or other input device. In embodimentsincluding a keypad 1012, the keypad 1012 can include (or cause displayof) the conventional numeric (0-9) and related keys (#, *), and otherkeys used for operating the mobile computing entities 804 a-f, and caninclude a full set of alphabetic keys or set of keys that can beactivated to provide a full set of alphanumeric keys. In addition toproviding input, the user input interface can be used, for example, toactivate or deactivate certain functions, such as screen savers and/orsleep modes.

As shown in FIG. 10, the mobile computing entities 804 a-f can alsoinclude a camera 1014, imaging device, and/or similar words used hereininterchangeably (e.g., still-image camera, video camera, IoT enabledcamera, IoT module with a low resolution camera, a wireless enabled MCU,and/or the like) configured to capture images. The mobile computingentities 804 a-f can be configured to capture images via the camera1014, and to store those imaging devices/cameras locally, such as in thevolatile memory 1016 and/or non-volatile memory 1018. As discussedherein, the mobile computing entities 804 a-f can be further configuredto match the captured image data with relevant location and/or timeinformation captured via the location determining aspects to providecontextual information/data, such as a time-stamp, date-stamp,location-stamp, and/or the like to the image data reflective of thetime, date, and/or location at which the image data was captured via thecamera 1014. The contextual data can be stored as a portion of the image(such that a visual representation of the image data includes thecontextual data) and/or can be stored as metadata associated with theimage data that can be accessible to various computing entities.

The mobile computing entities 804 a-f can include other inputmechanisms, such as scanners (e.g., barcode scanners), microphones,accelerometers, RFID readers, and/or the like configured to capture andstore various information types for the mobile computing entities 804a-f. For example, a scanner can be used to capture item information/datafrom an item indicator disposed on a surface of a shipment or otheritem. In certain embodiments, the mobile computing entities 804 a-f canbe configured to associate any captured input information/data, forexample, via the processing device 1006. For example, scan data capturedvia a scanner can be associated with image data captured via the camera1014 such that the scan data is provided as contextual data associatedwith the image data.

The mobile computing entities 804 a-f can also include volatile memory1016 and/or non-volatile memory 1018, which can be embedded and/orremovable. For example, the non-volatile memory 1018 can be ROM, PROM,EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks,CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory,racetrack memory, and/or the like. The volatile memory 1016 can be RAM,DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory,register memory, and/or the like. The volatile and non-volatile storageor memory can store databases, database instances, database managementsystems, information/data, applications, programs, program modules,scripts, source code, object code, byte code, compiled code, interpretedcode, machine code, executable instructions, and/or the like toimplement the functions of the mobile computing entities 804 a-f. Asindicated, this can include a user application that is resident on theentity or accessible through a browser or other user interface forcommunicating with the computing entity 802 and/or various othercomputing entities.

In another embodiment, the mobile computing entities 804 a-f can includeone or more components or functionality that are the same or similar tothose of the computing entity 802, as described in greater detail above.As will be recognized, these architectures and descriptions are providedfor exemplary purposes only and are not limiting to the variousembodiments.

4. Exemplary Item

A package, item, or shipment can be any tangible and/or physical object.As used herein, the terms “package,” “item,” and “shipment” are usedinterchangeably, and the terms are not to be construed as limiting apackage, item, or shipment to the singular or plural. An item can bepicked up and/or delivered by a carrier/transporter. In one embodiment,an item can be enclosed in one or more packages, parcels, bags,containers, loads, crates, items banded together, vehicle parts,pallets, drums, the like, and/or similar words used hereininterchangeably. An item can include the ability to communicate (e.g.,via a chip (e.g., an integrated circuit chip), RFID, NFC, Bluetooth,Wi-Fi, and any other suitable communication techniques, standards, orprotocols) with one another and/or communicate with various computingentities for a variety of purposes. For example, the item can beconfigured to communicate with one or more of the mobile computingentities 804 a-f using a short/long range communication technology, asdescribed in more detail below. Further, the item can have thecapabilities and components described with regard to the occupancycomputing entities, network 812, manual vehicle 800, autonomous vehicle810, computing entity 802, user computing entities, and/or the like. Forexample, the item can be configured to store item information asitem-specific data. In example embodiments, the item-specific data cancomprise one or more of a consignee name, consignee identifier, an itemidentifier, a service point (e.g., delivery location, delivery address,pickup location, pickup address), instructions for delivering the item,items delivery authorization code, item-specific data regarding whetherthe mobile computing entities 804 a-f is/are present at the servicepoint, and/or the like. In this regard, in some example embodiments, anitem can communicate send “to” address information/data, received “from”address information/data, unique identifier codes, and/or various otherinformation/data. In one embodiment, an item can include an itemidentifier, such as an alphanumeric identifier. Such an item identifiercan be represented as text, barcodes, tags, character strings, AztecCodes, MaxiCodes, Data Matrices, Quick Response (QR) Codes, electronicrepresentations, and/or the like. A unique item identifier (e.g.,123456789) can be used by the carrier to identify and track the item asit moves through the carrier's transportation network. Further, such anitem identifier can be affixed to an item by, for example, using asticker (e.g., label) with the unique item identifier printed thereon(in human and/or machine-readable form) or an RFID tag with the uniqueitem identifier stored therein.

In various embodiments, the item information/data comprises identifyinginformation/data corresponding to the item. The identifyinginformation/data can comprise information/data identifying the uniqueitem identifier associated with the item. Accordingly, upon providingthe identifying information/data to the item detail database (can beembedded in distribution computing entity), the item detail database canquery the stored item profiles to retrieve the item profilecorresponding to the provided unique identifier.

Moreover, the item information/data can comprise shippinginformation/data for the item. For example, the shippinginformation/data can identify an origin location (e.g., an originserviceable point), a destination location (e.g., a destinationserviceable point), a service level (e.g., Next Day Air, Overnight,Express, Next Day Air Early AM, Next Day Air Saver, Jetline, Sprintline,Secureline, 2nd Day Air, Priority, 2nd Day Air Early AM, 3 Day Select,Ground, Standard, First Class, Media Mail, SurePost, Freight, and/or thelike), whether a delivery confirmation signature is desired, requested,or required, and/or the like. In certain embodiments, at least a portionof the shipping information/data can be utilized as identifyinginformation/data to identify an item. For example, a destinationlocation can be utilized to query the item detail database to retrievedata about the item.

In certain embodiments, the item information/data comprisescharacteristic information/data identifying item characteristics. Forexample, the characteristic information/data can identify dimensions ofthe item (e.g., length, width, and height), a weight of the item,contents of the item, and/or the like. In certain embodiments, thecontents of the item can comprise a precise listing of the contents ofthe item (e.g., three widgets) and/or the contents can identify whetherthe item contains any hazardous materials (e.g., the contents canindicate whether the item contains one or more of the following: nohazardous materials, toxic materials, flammable materials, pressurizedmaterials, controlled substances, firearms, and/or the like).

5. Exemplary Item Information

As noted herein, various shipments/items can have an associated itemprofile, record, and/or similar words used herein interchangeably storedin an item detail database. The item profile can be utilized by thecarrier to track the current location of the item and to store andretrieve information/data about the item. For example, the item profilecan comprise electronic data corresponding to the associated item, andcan identify various shipping instructions for the item, variouscharacteristics of the item, and/or the like. The item profile cancomprise electronic data that identifies the type of item and/orspecifies the class of the item. The item profile can comprise data thatindicates one or more characteristics of the item, including SKU,height, width, depth, weight, size, dimensions, density, fragility,temperature sensitivity (e.g., item to be refrigerated for shipment),retail or wholesale value of the item, materials from which the item isconstructed (e.g., wood, metal, glass, fabric, compositions), itemcategory (e.g., clothing, books, movies, electronics, computers, office,home, garden, pet supplies, food and grocery, dining table, sofa, rug,mattress, jewelry, hardware, lumber, propane, steel, manufacturingmaterials or parts), and the like. The electronic data can be in aformat readable by various computing entities, such as the manualvehicle 800, the mobile computing entities 804 a-f, an autonomousvehicle control system, and/or the like. However, it should beunderstood that a computing entity configured for selectively retrievingelectronic data within various item profiles can comprise a formatconversion aspect configured to reformat requested data to be readableby a requesting computing entity.

In various embodiments, the item profile comprises identifyinginformation/data corresponding to the item. The identifyinginformation/data can comprise information/data identifying the uniqueitem identifier associated with the item. Accordingly, upon providingthe identifying information/data to the item detail database, the itemdetail database can query the stored item profiles to retrieve the itemprofile corresponding to the provided unique identifier.

Moreover, the item profiles can comprise shipping information/data forthe item. For example, the shipping information/data can identify anorigin location (e.g., an origin serviceable point), a destinationlocation (e.g., a destination serviceable point), a service level (e.g.,Next Day Air, Overnight, Express, Next Day Air Early AM, Next Day AirSaver, Jetline, Sprintline, Secureline, 2nd Day Air, Priority, 2nd DayAir Early AM, 3 Day Select, Ground, Standard, First Class, Media Mail,SurePost, Freight, and/or the like), whether a delivery confirmationsignature is desired, requested, or required, and/or the like. Incertain embodiments, at least a portion of the shipping information/datacan be utilized as identifying information/data to identify an item. Forexample, a destination location can be utilized to query the item detaildatabase to retrieve data about the item.

In certain embodiments, the item profile comprises characteristicinformation/data identifying item characteristics. For example, thecharacteristic information/data can identify dimensions of the item(e.g., length, width, and/or height), a weight of the item, contents ofthe item, and/or the like. In certain embodiments, the contents of theitem can comprise a precise listing of the contents of the item (e.g.,three widgets) and/or the contents can identify whether the itemcontains any hazardous materials (e.g., the contents can indicatewhether the item contains one or more of the following: no hazardousmaterials, toxic materials, flammable materials, pressurized materials,controlled substances, firearms, and/or the like).

6. Exemplary Item Profile

As noted herein, various shipments/items can have an associated itemprofile, record, and/or similar words used herein interchangeably storedin an item detail database. The item profile can be utilized by thecarrier to track the current location of the item and to store andretrieve information/data about the parcel/item/shipment. For example,the item profile can comprise electronic data corresponding to theassociated parcel/item/shipment, and can identify various shippinginstructions for the parcel/item/shipment, various characteristics ofthe parcel/item/shipment, and/or the like. The electronic data can be ina format readable by various computing entities, such as a computingentity 802, a mobile computing entities 804 a-f, an autonomous vehiclecontrol system, and/or the like. However, it should be understood that acomputing entity configured for selectively retrieving electronic datawithin various item profiles can comprise a format conversion aspectconfigured to reformat requested data to be readable by a requestingcomputing entity. In various embodiments, the item profile comprisesidentifying information/data corresponding to the parcel/item/shipment.The identifying information/data can comprise information/dataidentifying the unique item identifier associated with theparcel/item/shipment. Accordingly, upon providing the identifyinginformation/data to the item detail database, the item detail databaseor other data store can query the stored item profiles to retrieve theitem profile corresponding to the provided unique identifier. Moreover,the item profiles can comprise shipping information/data for theparcel/item/shipment. For example, the shipping information/data canidentify an origin location (e.g., an origin serviceable point), adestination location (e.g., a destination serviceable point), a servicelevel (e.g., Next Day Air, Overnight, Express, Next Day Air Early AM,Next Day Air Saver, Jetline, Sprintline, Secureline, 2nd Day Air,Priority, 2nd Day Air Early AM, 3 Day Select, Ground, Standard, FirstClass, Media Mail, SurePost, Freight, High value CHC (critical healthcare) shipments, and/or the like), whether a delivery confirmationsignature is desired, requested, or required, and/or the like. Incertain embodiments, at least a portion of the shipping information/datacan be utilized as identifying information/data to identify aparcel/item/shipment. For example, a destination location can beutilized to query the item detail database to retrieve data about theparcel/item/shipment. In certain embodiments, the item profile comprisescharacteristic information/data identifying item characteristics. Forexample, the characteristic information/data can identify dimensions ofthe item (e.g., length, width, and height), a weight of theparcel/item/shipment, contents of the parcel/item/shipment, and/or thelike. In certain embodiments, the contents of the item can comprise aprecise listing of the contents of the item (e.g., three widgets) and/orthe contents can identify whether the item contains any hazardousmaterials (e.g., the contents can indicate whether the item contains oneor more of the following: no hazardous materials, toxic materials,flammable materials, pressurized materials, controlled substances,firearms, and/or the like).

7. Exemplary Autonomous Vehicle

As utilized herein, an autonomous vehicle 810 can be configured fortransporting one or more shipments. Although the autonomous vehicle(s)810 are discussed herein as comprising unmanned aerial vehicles (UAVs),it should be understood that the autonomous vehicles can be ground-basedin certain embodiments. FIG. 11 illustrates an example autonomousvehicle 810 that can be utilized in various embodiments. As shown inFIG. 11, the autonomous vehicle 810 is embodied as a UAV generallycomprising a UAV chassis 1100 and a plurality of propulsion members 1102extending outwardly from the UAV chassis 1100 (in certain embodiments,the propulsion members 1102 are surrounded by propeller guards 1104).The UAV chassis 1100 generally defines a body of the UAV, which thepropulsion members 1102 (e.g., propellers having a plurality of bladesconfigured for rotating within a propeller guard circumscribing thepropellers) are configured to lift and guide during flight. According tovarious embodiments, the UAV chassis 1100 can be formed from anymaterial of suitable strength and weight (including sustainable andreusable materials), including but not limited to composite materials,aluminum, titanium, polymers, and/or the like, and can be formed throughany suitable process.

In the embodiment depicted in FIG. 11, the autonomous vehicle 810 is ahexacopter and includes six separate propulsion members 1102, eachextending outwardly from the UAV chassis 1100. However, as will beappreciated from the description herein, the autonomous vehicle 810 caninclude any number of propulsion members 1102 suitable to provide liftand guide the autonomous vehicle 810 during flight. The propulsionmembers 1102 are configured to enable vertical locomotion (e.g., lift)and/or horizontal locomotion, as shown in the example embodiment of FIG.11, as well as enabling roll, pitch, and yaw movements of the autonomousvehicle 810. Although not shown, it should be understood that theautonomous vehicle(s) 810 can comprise any of a variety of propulsionmechanisms, such as balloon-based lift mechanisms (e.g., enablinglighter-than-air transportation), wing-based lift mechanisms,turbine-based lift mechanisms, and/or the like.

In the illustrated embodiment, the propulsion members 1102 areelectrically powered (e.g., by an electric motor that controls the speedat which the propellers rotate). However, the propulsion members 1102can be powered by internal combustion engines (e.g., alcohol-fueled,oil-fueled, gasoline-fueled, and/or the like) driving an alternator,hydrogen fuel-cells, and/or the like.

Moreover, as shown in FIG. 11, the lower portion of the UAV chassis 1100is configured to receive and engage a parcel carrier 1106 configured forselectively supporting an item to be delivered from a manual vehicle 800to a delivery destination. The parcel carrier 1106 can define the lowestpoint of the autonomous vehicle 810 when secured relative to the UAVchassis 1100 of the autonomous vehicle 810, such that an item carried bythe autonomous vehicle 810 can be positioned below the UAV chassis 1100of the autonomous vehicle 810 during transit. In certain embodiments,the parcel carrier 1106 can comprise one or more parcel engagement arms1108 configured to detachably secure relative to the autonomous vehicle810. In such embodiments, the item can be suspended by the parcelengagement arms 1108 below the autonomous vehicle 810, such that it canbe released from the autonomous vehicle 810 while the autonomous vehicle810 hovers over a desired delivery destination. However, it should beunderstood that the parcel carrier 1106 can have any of a variety ofconfigurations enabling the autonomous vehicle 810 to support an itemduring transit.

In certain embodiments, the parcel carrier 1106 can be detachablysecured relative to the UAV chassis 1100, for example, such thatalternative parcel carriers having items secured thereto can bealternatively connected relative to the UAV chassis 1100 for delivery.In certain embodiments, a UAV can be configured to deliver an itemsecured within a parcel carrier 1106, and return to a manual vehicle 800where the parcel carrier 1106, now empty due to the delivery of the itemthat was previously secured therein, can be detached from the autonomousvehicle 810 and a separate, new parcel carrier (not shown) having asecond item can be secured to the UAV chassis 1100.

As indicated hereinafter regarding FIG. 12, which illustrates an examplemanual vehicle 800 according to various embodiments, the autonomousvehicle 810 can be configured to selectively engage a portion of themanual vehicle 800 such that the manual vehicle 800 can transport theautonomous vehicle 810 and/or other similar autonomous vehicles. Forexample, the UAV chassis 1100 can be configured to engage one or morevehicle guide mechanisms secured relative to the manual vehicle 800 todetachably secure the autonomous vehicle 810 relative to the manualvehicle 800 when not delivering shipments/items. As discussed herein,the guide mechanism of a manual vehicle 800 can be configured to enablean autonomous vehicle 810 to autonomously take-off or depart from themanual vehicle 800 to initiate a delivery activity and/or toautonomously land or arrive at the manual vehicle 800 to conclude adelivery activity.

Moreover, the autonomous vehicle 810 additionally comprises an onboardcontrol system embodied as one or more of the mobile computing entities804 a-f that include a plurality of sensing devices that assist innavigating the autonomous vehicle 810 during flight. For example, thecontrol system is configured to control movement of the autonomousvehicle 810, navigation of the autonomous vehicle 810, obstacleavoidance, item delivery, and/or the like. Although not shown, thecontrol system can additionally comprise one or more user interfaces,which can comprise an output mechanism and/or an input mechanismconfigured to receive user input. For example, the user interface can beconfigured to enable autonomous vehicle technicians to review diagnosticinformation/data relating to the autonomous vehicle 810, and/or a userof the autonomous vehicle 810 can utilize the user interface to inputand/or review information/data indicative of a destination location forthe autonomous vehicle 810.

The plurality of sensing devices are configured to detect objects aroundthe autonomous vehicle 810 and provide feedback to an autonomous vehicleonboard control system to assist in guiding the autonomous vehicle 810in the execution of various operations, such as take-off, flightnavigation, and landing, as will be described in greater detail herein.In certain embodiments, the autonomous vehicle control system comprisesa plurality of sensors including ground landing sensors, vehicle landingsensors, flight guidance sensors, and one or more imagingdevices/cameras (e.g., that utilize object recognition algorithms toidentify objects). The vehicle landing sensors can be positioned on alower portion of the UAV chassis 1100 and assist in landing theautonomous vehicle 810 on a manual vehicle 800 as will be described ingreater detail herein. The vehicle landing sensors can include one ormore imaging devices/cameras (e.g., video imaging devices/cameras and/orstill imaging devices/cameras) and one or more altitude sensors (e.g.,Light Detection and Ranging (LIDAR) sensors, laser-based distancesensors, infrared distance sensors, ultrasonic distance sensors, opticalsensors and/or the like). Being located on the lower portion of the UAVchassis 1100, the vehicle landing sensors are positioned below thepropulsion members 1102 and have a line of sight with the manualdelivery vehicle's UAV support mechanism when the autonomous vehicle 810approaches the manual vehicle 800 during landing.

The autonomous vehicle's one or more imaging devices/cameras can also bepositioned on the lower portion of the UAV chassis 1100, on propellerguards 1104, and/or the like. The one or more imaging devices/camerascan include video and/or still imaging devices/cameras, and can captureimages and/or video of the flight of the autonomous vehicle 810 during adelivery process, and can assist in verifying or confirming delivery ofan item to a destination, as will be described in greater detail herein.Being located on the lower portion of the UAV chassis 1100, the one ormore imaging devices/cameras are positioned below the propulsion members1102 and have an unobstructed line of sight to view the flight of theautonomous vehicle 810. Moreover, as discussed specifically in referenceto the mobile computing entities 804 a-f, the one or more imagingdevices/cameras disposed on the UAV can be configured for capturingimages of one or more items/shipments before picking up thoseitems/shipments, after dropping off those items/shipments, duringtransit of the items/shipments, and/or the like.

In particular embodiments, the information/data collection device 814can include, be associated with, or be in wired or wirelesscommunication with one or more processors (various exemplary processorsare described in greater detail below), one or more location-determiningdevices or one or more location sensors (e.g., Global NavigationSatellite System (GNSS) sensors), indoor location sensors, (e.g.,Bluetooth sensors, Wi-Fi sensors, GPS sensors, beacon sensors, and/orthe like), one or more real-time clocks, a J-Bus protocol architecture,one or more electronic control modules (ECM), one or more communicationports for receiving information/data from various sensors (e.g., via aCAN-bus), one or more communication ports for transmitting/sendinginformation/data, one or more RFID tags/sensors, one or more powersources, one or more information/data radios for communication with avariety of communication networks, one or more memory modules, and oneor more programmable logic controllers (PLC). It should be noted thatmany of these components can be located in the autonomous vehicle 810but external to the information/data collection device 814.

In some embodiments, the one or more location sensors, modules, orsimilar words used herein interchangeably can be one of severalcomponents in wired or wireless communication with or available to theinformation/data collection device 814. Moreover, the one or morelocation sensors can be compatible with satellite 806, such as Low EarthOrbit (LEO) satellite systems, Department of Defense (DOD) satellitesystems, the European Union Galileo positioning systems, the ChineseCompass navigation systems, Indian Regional Navigational satellitesystems, and/or the like. This information/data can be collected using avariety of coordinate systems, such as the Decimal Degrees (DD);Degrees, Minutes, Seconds (DMS); Universal Transverse Mercator (UTM);Universal Polar Stereographic (UPS) coordinate systems; and/or the like.

As discussed herein, triangulation and/or proximity-based locationdeterminations can be used in connection with a device associated with aparticular autonomous vehicle 810 and with various communication points(e.g., cellular towers, Wi-Fi access points, and/or the like) positionedat various locations throughout a geographic area to monitor thelocation of the manual vehicle 800 and/or its operator. The one or morelocation sensors can be used to receive latitude, longitude, altitude,heading or direction, geocode, course, position, time, locationidentifying information/data, and/or speed information/data (e.g.,referred to herein as location information/data and further describedherein below). The one or more location sensors can also communicatewith the computing entity 802, the information/data collection device814, mobile computing entities 804 a-f, and/or similar computingentities.

In some embodiments, the ECM can be one of several components incommunication with and/or available to the information/data collectiondevice 814. The ECM, which can be a scalable and subservient device tothe information/data collection device 814, can have information/dataprocessing capability to decode and store analog and digital inputsreceived from, for example, vehicle systems and sensors. The ECM canfurther have information/data processing capability to collect andpresent location information/data to the J-Bus (which can allowtransmission to the information/data collection device 814), and outputlocation identifying information/data, for example, via a display and/orother output device (e.g., a speaker).

As indicated, a communication port can be one of several componentsavailable in the information/data collection device 814 (or be in or asa separate computing entity). Embodiments of the communication port caninclude an Infrared information/data Association (IrDA) communicationport, an information/data radio, and/or a serial port. The communicationport can receive instructions for the information/data collection device814. These instructions can be specific to the manual vehicle 800 inwhich the information/data collection device 814 is installed, specificto the geographic area and/or serviceable point to which the manualvehicle 800 will be traveling, specific to the function the vehicleserves within a fleet, and/or the like. In particular embodiments, theinformation/data radio can be configured to communicate with a WWAN,WLAN, WPAN, or any combination thereof. For example, theinformation/data radio can communicate via various wireless protocols,such as 802.11, GPRS, UMTS, CDMA2000, 1×RTT, WCDMA, TD-SCDMA, LTE,E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX, UWB, IR protocols, Bluetoothprotocols (including BLE), wireless USB protocols, and/or any otherwireless protocol. As yet other examples, the communication port can beconfigured to transmit and/or receive information/data transmissions vialight-based communication protocols (e.g., utilizing specific lightemission frequencies, wavelengths (e.g., visible light, infrared light,and/or the like), and/or the like to transmit data), via sound-basedcommunication protocols (e.g., utilizing specific sound frequencies totransmit data), and/or the like.

8. Exemplary Manual Vehicle

As discussed herein, a manual vehicle 800 can be a user (e.g., human)operable delivery vehicle configured for transporting a vehicleoperator, a plurality of items, and one or more autonomous vehicle(s)810 along a delivery route. However, it should be understood that incertain embodiments, even though the term “manual vehicle” is used, thisis simply to distinguish it in the description from the autonomousvehicle 810. Thus, the manual vehicle 800 can itself be autonomous orsemi-autonomous. For example, the manual vehicle 800 is a self-drivingvehicle in some embodiments such that no physical person or user isneeded to operate the manual vehicle 800. In certain embodiments, anautonomous vehicle can be configured as an autonomous base vehicleconfigured to carry a plurality of items, one or more smaller, auxiliaryautonomous vehicles (e.g., autonomous vehicle 810 described in detailherein), a human delivery personnel (e.g., who can complete variousdeliveries from the manual vehicle 800 to respective destinationlocations), and/or the like. For example, a manual vehicle 800 can be amanned or an unmanned tractor, truck, car, motorcycle, moped, Segway,bicycle, golf cart, hand truck, cart, trailer, tractor and trailercombination, van, flatbed truck, vehicle, drone, airplane, helicopter,boat, barge, and/or any other form of object for moving or transportingpeople, UAVs, and/or shipments/items (e.g., one or more packages,parcels, bags, containers, loads, crates, items banded together, vehicleparts, pallets, drums, the like, and/or similar words used hereininterchangeably). In particular embodiments, each manual vehicle 800 canbe associated with a unique vehicle identifier (such as a vehicle ID)that uniquely identifies the manual vehicle 800.

In various embodiments, the manual vehicle 800 comprises one or moreautonomous vehicle support mechanisms, as shown in FIG. 12. Theautonomous vehicle support mechanisms can be configured to enable theautonomous vehicle(s) 810 to launch and land at the manual vehicle 800while completing autonomous deliveries. Moreover, although not shown,the interior of the manual vehicle 800 can comprise a cargo areaconfigured for storing a plurality of items, a plurality of autonomousvehicles such as autonomous vehicle 810, a plurality of autonomousvehicle components, and/or the like.

Moreover, the manual vehicle 800 can comprise and/or be associated withone or more of the mobile computing entities 804 a-f, devices, and/orsimilar words used herein interchangeably. The mobile computing entities804 a-f can comprise, for example, an information/data collection device814 or other computing entities.

In particular embodiments, the information/data collection device 814can include, be associated with, or be in wired or wirelesscommunication with one or more processors (various exemplary processorsare described in greater detail below), one or more location-determiningdevices or one or more location sensors (e.g., GNSS sensors), one ormore telematics sensors, one or more real-time clocks, a J-Bus protocolarchitecture, one or more ECMs, one or more communication ports forreceiving telematics information/data from various sensors (e.g., via aCAN-bus), one or more communication ports for transmitting/sendinginformation/data, one or more RFID tags/sensors, one or more powersources, one or more information/data radios for communication with avariety of communication networks, one or more memory modules, and oneor more programmable logic controllers (PLC). It should be noted thatmany of these components can be located in the manual vehicle 800 butexternal to the information/data collection device 814.

In particular embodiments, the one or more location sensors, modules, orsimilar words used herein interchangeably can be one of severalcomponents in wired or wireless communication with or available to theinformation/data collection device 814. Moreover, the one or morelocation sensors can be compatible with satellite 806, LEO satellitesystems, DOD satellite systems, the European Union Galileo positioningsystems, the Chinese Compass navigation systems, Indian RegionalNavigational satellite systems, and/or the like, as discussed above inreference to the autonomous delivery vehicle. Alternatively,triangulation can be used in connection with a device associated with aparticular vehicle and/or the vehicle's operator and with variouscommunication points (e.g., cellular towers or Wi-Fi access points)positioned at various locations throughout a geographic area to monitorthe location of the manual vehicle 800 and/or its operator. The one ormore location sensors can be used to receive latitude, longitude,altitude, heading or direction, geocode, course, position, time, and/orspeed information/data (e.g., referred to herein as telematicsinformation/data and further described herein below). The one or morelocation sensors can also communicate with the computing entity 802, theinformation/data collection device 814, mobile computing entities 804a-f, and/or similar computing entities.

In particular embodiments, the ECM can be one of several components incommunication with and/or available to the information/data collectiondevice 814. The ECM, which can be a scalable and subservient device tothe information/data collection device 814, can have information/dataprocessing capability to decode and store analog and digital inputs fromvehicle systems and sensors (e.g., location sensor). The ECM can furtherhave information/data processing capability to collect and presentcollected information/data to the J-Bus (which can allow transmission tothe information/data collection device 814).

As indicated, a communication port can be one of several componentsavailable in the information/data collection device 814 (or be in or asa separate computing entity). Embodiments of the communication port caninclude an IrDA communication port, an information/data radio, and/or aserial port. The communication port can receive instructions for theinformation/data collection device 814. These instructions can bespecific to the manual vehicle 800 in which the information/datacollection device 814 is installed, specific to the geographic area inwhich the manual vehicle 800 will be traveling, specific to the functionthe manual vehicle 800 serves within a fleet, and/or the like. Inparticular embodiments, the information/data radio can be configured tocommunicate with WWAN, WLAN, WPAN, or any combination thereof, asdiscussed in reference to the autonomous vehicle, above.

9. Exemplary Conveying Mechanism

As shipments/items are moved through a carrier's logistics networkbetween corresponding origins and destinations, those shipments/itemscan pass through one or more carrier sort locations. Each carrier sortlocation can comprise one or more conveying mechanisms (e.g., conveyorbelts, chutes, and/or the like), configured to move shipments/itemsbetween incoming locations (e.g., incoming vehicles) to correspondingoutbound vehicles destined for later locations along aparcel/item/shipment's intended transportation path between the originand destination.

FIG. 13 includes an illustration of a conveying mechanism 1300 accordingto particular embodiments of the present disclosure. As shown in FIG. 13and FIG. 14, the conveying mechanism 1300 can be used with an imagecapture system 1400 having multiple views and/or multiple fields-of-view(e.g., comprising many image acquisition devices) for acquiringinformation/data (including image information/data) regarding an item.As mentioned herein, each item can include an item identifier. Such itemidentifiers can be represented as text, barcodes, Aztec Codes,MaxiCodes, Data Matrices, Quick Response (QR) Codes, electronicrepresentations, tags, character strings, and/or the like. The uniqueitem identifier can be used by the carrier to identify and track theitem as it moves through the carrier's transportation network. Further,such item identifiers can be affixed to items by, for example, using asticker (e.g., label) with the unique item identifier printed thereon(in human and/or machine-readable form) or an RFID tag with the uniqueitem identifier stored therein. Accordingly, the image acquisitiondevices 1402 a, 1402 b, 1402 c, 1402 d, and 1402 e (i.e., 1402 a-e) ofFIG. 14 can be capable of acquiring data (including item identifiers)relevant to each parcel/item/shipment, including item identifierinformation/data, item condition information/data, and/or the like forshipments/items traveling along a corresponding conveying mechanism 1300(e.g., conveyor belt, slide, chute, bottle conveyor, open or enclosedtrack conveyor, I-beam conveyor, cleated conveyor, and/or the like).

As indicated, the image acquisition devices 1402 a-e can be part of animage capture system 1400 configured to capture images (e.g., imageinformation/data) of shipments/items (and/or item identifiers) movingalong the conveying mechanism 1300. Each of the image acquisitiondevices 1402 a-e can have a corresponding fields-of-view 1404 a, 1404 b,1404 c, 1404 d, and 1404 e (i.e., 1404 a-e), as shown in FIG. 14. Therecan be overlap between the fields-of-view 1404 a-e, in some embodiments.For example, the image acquisition devices 1402 a-e can include or be avideo camera, camcorder, still camera, web camera, Single-Lens Reflex(SLR) camera, high-speed camera, and/or the like. In variousembodiments, the image acquisition devices 1402 a-e can be configured torecord high-resolution image data and/or to capture image data at a highspeed (e.g., utilizing a frame rate of at least 60 frames per second).Alternatively, the image acquisition devices 1402 a-e can be configuredto record low-resolution image data (e.g., images comprising less than480 horizontal scan lines) and/or to capture image data at a low speed(e.g., utilizing a frame rate less than 60 frames per second). As willbe understood by those skilled in the art, the image acquisition devices1402 a-e can be configured to operate with various combinations of theabove features (e.g., capturing images with less than 480 horizontalscan lines and utilizing a frame rate of at least 60 frames per second,or capturing images with at least 480 horizontal scan lines andutilizing a frame rate less than 60 frames per second). In variousembodiments, the image acquisition devices 1402 a-e can be configured tocapture image data of the shipments/items and conveying mechanism 1300of sufficient quality that a user viewing the image data on the displaycan identify each item represented in the displayed image data. Forexample, in embodiments wherein the conveying mechanism 1300 andshipments/items are moving at a high rate of speed, the imageacquisition devices 1402 a-e can be configured to capture image data ata high speed. As will be recognized, the image data can be captured inor converted to a variety of formats, such as Joint Photographic ExpertsGroup (JPEG), Motion JPEG (MJPEG), Moving Picture Experts Group (MPEG),Graphics Interchange Format (GIF), Portable Network Graphics (PNG),Tagged Image File Format (TIFF), bitmap (BMP), H.264, H.263, Flash Video(FLV), Hypertext Markup Language 5 (HTML5), VP6, VP8, and/or the like.In certain embodiments, various features (e.g., text, objects ofinterest, codes, item identifiers, and/or the like) can be extractedfrom the image data.

As described in more detail with respect to FIG. 14 herein, in someembodiments, the image capture system 1400 can alternatively oradditionally be located within various other points or areas within aparcel carrier's (e.g., parcel carrier 1106) logistic network other thanthe environment associated with FIG. 13.

The image capture system 1400 can additionally include or be one or morescanners, readers, interrogators, and similar words used hereininterchangeably configured for capturing item indicia for each item(e.g., including item identifiers). For example, the image capturesystem 1400 can include one or more image acquisition devices 1402 a-e,such as an optical reading device, a barcode scanner, an RFID reader,and/or the like configured to recognize and identify item identifiersassociated with each parcel/item/shipment. In particular embodiments,the image acquisition devices 1402 a-e can be capable of receivingvisible light, infrared light, radio transmissions, and/or othertransmissions capable of transmitting information to image acquisitiondevices 1402 a-e. Similarly, image acquisition devices 1402 a-e caninclude or be used in association with various lighting, such as lightemitting diodes (LEDs), Infrared lights, array lights, strobe lights,and/or other lighting mechanisms to sufficiently illuminate the zones ofinterest to capture image data for analysis.

Similar to mobile computing entities 804 a-f described above, inparticular embodiments, the conveying mechanism 1300, the image capturesystem 1400, and/or the image acquisition devices 1402 a-e individuallycan also include one or more communications interfaces for communicatingwith various computing entities, such as by communicatinginformation/data, content, and/or similar terms used hereininterchangeably that can be transmitted, received, operated on,processed, displayed, stored, and/or the like. Such communication can beexecuted using a wired data transmission protocol, such as FDDI, DSL,Ethernet, ATM, frame relay, DOCSIS, or any other wired transmissionprotocol. Similarly, the conveying mechanism 1300 can be configured tocommunicate via wireless external communication networks using any of avariety of protocols, as previously described hereinabove.

As will be understood by those skilled in the art, the image capturesystem 1400 can include any number of image acquisition devices 1402 a-eas shown in FIG. 14. In various embodiments, one or more additionalimage acquisition devices can be used to capture additional image dataat one or more additional locations along the conveying mechanism 1300or an additional conveying mechanism. Such additional image acquisitiondevices can be located, for example, after the flow of items along theconveying mechanism 1300 is disturbed (e.g., the flow of items isculled, merged with an additional flow of items, or diverted to anadditional conveying mechanism). Alternatively, one or more additionalimage acquisition devices can be located along the conveying mechanism1300, such that the one or more additional image acquisition devices cancapture updated image data after one or more of the items can have beenremoved from the conveying mechanism 1300. In various embodiments, theone or more additional image acquisition devices can include componentssubstantially similar to the image capture system 1400. For example, theone or more additional image acquisition devices can include or beassociated with one or more imaging devices and one or more scanners,readers, interrogators, and similar words used herein interchangeably,as described above in regards to the image capture system 1400. However,the one or more additional image acquisition devices can include fewercomponents than image acquisition devices 1402 a-e.

CONCLUSION

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing description and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation, unlessdescribed otherwise.

What is claimed is:
 1. A computer-implemented method comprising:receiving, by a computing device, an instance from an entity serverduring a predetermined period of time, wherein the received instanceincludes a defined instance value; determining, by the computing device,that the received instance corresponds to a first class of a definedindex having a plurality of defined classes, a plurality of definedtiers, and a plurality of defined baseline ratios, each of the pluralityof defined tiers comprising an instance value range, and each of theplurality of defined baseline ratios being associated with a particularcombination of a defined class and a defined tier; determining, by thecomputing device, the defined instance value included in the receivedinstance corresponds to a first instance value range of one of theplurality of defined tiers; determining, by the computing device, thatthe received instance is associated with a first baseline ratio of theplurality of defined baseline ratios based on the received instancecorresponding to the first class and the defined instance valuecorresponding to the first instance value range of one of the pluralityof defined tiers; calculating, by the computing device, a contributionvalue associated with the received instance based on the definedinstance value multiplied by the first baseline ratio determined to beassociated with the received instance; calculating, by the computingdevice, a delivery value associated with the received instance;calculating, by the computing device, a cumulative contribution amountassociated with the entity server based on the calculated contributionvalue associated with the received instance and a determined conclusionof the predetermined period of time; calculating, by the computingdevice, a cumulative delivery value associated with the predeterminedperiod of time, wherein the cumulative delivery value is calculatedbased on a determined delivery value associated with the receivedinstance; and reconciling, by the computing device, the calculatedcumulative contribution amount with the cumulative delivery value forthe predetermined period of time.
 2. A system comprising: acommunications interface that receives an instance from an entity serverduring a predetermined period of time, wherein the received instanceincludes a defined instance value; an instance assignment module that:determines that the received instance corresponds to a first class of adefined index having a plurality of defined classes, a plurality ofdefined tiers, and a plurality of defined baseline ratios, each of theplurality of defined tiers comprising an instance value range, and eachof the plurality of defined baseline ratios being associated with aparticular combination of a defined class and a defined tier; determinesthat the defined instance value included in the received instancecorresponds to a first instance value range of one of the plurality ofdefined tiers; and determines that the received instance is associatedwith a first baseline ratio of the plurality of defined baseline ratiosbased on the received instance corresponding to the first class and thedefined instance value corresponding to the first instance value rangeof one of the plurality of defined tiers; and a reconciliation modulethat: calculates a contribution value associated with the receivedinstance based on the defined instance value multiplied by the firstbaseline ratio determined to be associated with the received instance;calculates a delivery value associated with the received instance;calculates a cumulative contribution amount associated with the entityserver based on the calculated contribution value associated with thereceived instance and a determined conclusion of the predeterminedperiod of time; calculates a cumulative delivery value associated withthe predetermined period of time, wherein the cumulative delivery valueis calculated based on a determined delivery value associated with thereceived instance; and reconciles the calculated cumulative contributionamount with the calculated cumulative delivery value for thepredetermined period of time.
 3. A computer-implemented methodcomprising: for each of one or more instances fulfilled by an entitythat corresponds to a first class of an index having a plurality ofclasses, determining an instance value multiplied by a baseline ratioassociated with the first class of the index; for each of one or moreinstances fulfilled by the entity that corresponds to the first class,determining a delivery value of a delivery associated with the instance;determining a cumulative contribution amount of the one or moreinstances fulfilled by the entity during the predetermined period oftime; determining a cumulative delivery value of deliveries associatedwith the one or more instances fulfilled by the entity during thepredetermined period of time; and reconciling the cumulativecontribution amount with the cumulative delivery value for the entityfor the predetermined period of time.
 4. The method of claim 3, furthercomprising based on reconciling the cumulative contribution amount withthe cumulative delivery value, determining the entity corresponds to asecond class of the index, the second class is associated with abaseline ratio that is different from the baseline ratio associated withthe first class.
 5. The method of claim 4, wherein the baseline ratioassociated with the second class is greater than the baseline ratioassociated with the first class.
 6. The method of claim 4, wherein thebaseline ratio associated with the second class is less than thebaseline ratio associated with the first class.
 7. The method of claim3, wherein the method is performed in a reoccurring fashion for aplurality of time periods and a plurality of entities, each time periodcorresponding to the predetermined period of time.
 8. The method ofclaim 3, further comprising generating the index based on historicalinstance information and historical delivery information, wherein theindex includes a plurality of tiers, and wherein each combination ofeach of the plurality of classes and each of the plurality of tiers isassociated with a baseline ratio.
 9. The method of claim 3, whereindetermining the entity corresponds to the first class of the indexhaving the plurality of classes further comprises determining one ormore of an average parcel volume, an average delivery zone, an overalldelivery density, or a seasonal delivery density.
 10. The method ofclaim 9, wherein determining the entity corresponds to the first classof the index having the plurality of classes further comprisesdetermining an average parcel weight.
 11. The method of claim 3, furthercomprising modifying the predetermined period of time for a subsequentreconciliation, wherein the predetermined period of time is adjustedbased on the cumulative delivery value for the entity.
 12. The method ofclaim 11, wherein modifying the predetermined period of time for asubsequent reconciliation comprises shortening the predetermined periodof time when the cumulative delivery value for the entity belonging tothe first class meets or exceeds the cumulative contribution amount. 13.The method of claim 11, wherein modifying the predetermined period oftime for a subsequent reconciliation comprises lengthening thepredetermined period of time when the cumulative delivery value for theentity belonging to the first class is less than the cumulativecontribution amount.
 14. The method of claim 3, further comprising,based on reconciling the cumulative contribution amount with thecumulative delivery value, adjusting the baseline ratio of one or moreof the plurality of tiers in the index.
 15. The method of claim 3,wherein the method further comprises: based on reconciling thecumulative contribution amount with the cumulative delivery value,determining the entity corresponds to a second class of the index, thesecond class is associated with a baseline ratio that is different fromthe baseline ratio associated with the first class; and assigning theentity to the second class in the index.
 16. The method of claim 15,wherein the method further comprises: subsequent to assigning the entityto the second class in the index: determining an instance valuemultiplied by the baseline ratio associated with the second class foreach of the one or more instances fulfilled by the entity in asubsequent predetermined period of time; determining a delivery valueassociated with delivery of the instance for each of the one or moreinstances fulfilled by the entity in a subsequent predetermined periodof time; determining a cumulative contribution amount of the one or moreinstances fulfilled by the entity during the subsequent predeterminedperiod of time; determining a cumulative delivery value associated withdeliveries of the one or more instances during the subsequentpredetermined period of time; and reconciling the cumulativecontribution amount with the cumulative delivery value for the entityfor the subsequent predetermined period of time.
 17. The method of claim3, wherein the method is performed in a reoccurring fashion for aplurality of predetermined periods of time and a plurality of entities.18. The method of claim 17, wherein the method further comprises foreach of one or more instances fulfilled by the plurality of entities forthe plurality of time periods, monitoring item-specific characteristicsof the instance.
 19. The method of claim 18, wherein the method furthercomprises, based on reconciling the cumulative contribution amount withthe cumulative delivery value, and based on the item-specificcharacteristics monitoring of the one or more instances fulfilled by theplurality of entities for the plurality of time periods, reducing theplurality of classes in number to simplify the index and maintaining agreatest baseline ratio for each of the plurality of classes in theindex.